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_BT=y
CONFIG_BT_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`
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2017-08-09 14:21:11 +08:00			`CONFIG_BT=y`
			`CONFIG_BT_HCI_RAW=y`