mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-01 16:42:39 +00:00
2975ca0754
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> |
||
|---|---|---|
| .. | ||
| src | ||
| 96b_nitrogen.overlay | ||
| generic.conf | ||
| Makefile | ||
| microbit.conf | ||
| nrf5.conf | ||
| nrf51_blenano.overlay | ||
| nrf51_pca10028.overlay | ||
| nrf52_blenano2.overlay | ||
| nrf52_pca10040.overlay | ||
| nrf52840_pca10056.overlay | ||
| README.rst | ||
| sample.yaml | ||
.. _bluetooth-hci-uart-sample: Bluetooth: HCI UART #################### Overview ********* Expose Zephyr Bluetooth Controller support over UART to another device/CPU using the H:4 HCI transport protocol (requires HW flow control from the UART) Requirements ************ * BlueZ running on the host, or * A board with BLE support Building and Running ******************** This sample can be found under :file:`samples/bluetooth/hci_uart` in the Zephyr tree. See :ref:`bluetooth setup section <bluetooth_setup>` for details.