zephyr/samples/bluetooth/hci_uart/generic.conf

CONFIG_CONSOLE=n
CONFIG_STDOUT_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_BLUETOOTH=y
CONFIG_BLUETOOTH_HCI_RAW=y
Bluetooth: HCI UART app to run Zephyr as a BLE Controller Add a new sample application in sample/bluetooth/hci-uart that acts as a bridge between a UART and the BLE Controller. It receives commands and ACL data in H4 format over the UART and passes them on to the BLE Controller to be processed. It also conversely forwards all events and incoming ACL data generated by the BLE Controller to the UART. The application uses the hci_raw interface to pipe the data to and from the BLE Controller and UART. Change-Id: Iff7696166a82fe363b2ad4e1abea40103899f927 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2016-10-16 03:19:08 +08:00			`CONFIG_CONSOLE=n`
			`CONFIG_STDOUT_CONSOLE=n`
			`CONFIG_UART_CONSOLE=n`
			`CONFIG_SERIAL=y`
			`CONFIG_UART_INTERRUPT_DRIVEN=y`
			`CONFIG_BLUETOOTH=y`
Bluetooth: Kconfig: Restructure for a more logical hierarchy Restructure the Bluetooth options more logically. - Both host and controller are now behind the same high level CONFIG_BLUETOOTH. - Selecting controller support disables other HCI driver selection, so the controller isn't in the same list as HCI drivers any more. - Under the top-level there's a "Custom stack" option, which when enabled opens up the option of choosing CONFIG_NBLE. There are various other cleanups and simplifications in this patch as well, since splitting these up would have been fairly tricky while making sure all test cases still build. Change-Id: I5bb715cb9d20201cb8b72fbd149c8a09a4b2d7d2 Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2016-11-09 18:23:21 +08:00			`CONFIG_BLUETOOTH_HCI_RAW=y`