zephyr

History

Johan Hedberg 2975ca0754 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 11:14:19 +03:00
..
src	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00
Makefile	Bluetooth: samples: Use consistent naming for HCI apps	2016-11-09 08:57:52 +02:00
README.rst	doc: add labels to bluetooth sample docs	2017-04-04 19:51:27 +00:00
prj.conf	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00
prj_tinytile.conf	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00
sample.yaml	samples: mark samples that require usb_device support	2017-07-07 09:01:01 -05:00

README.rst

.. _bluetooth-hci-usb-sample:

Bluetooth: HCI USB
##################

Overview
********

Make a USB Bluetooth dongle out of Zephyr. Requires USB device support from the
board it runs on (e.g. :ref:`arduino_101` has this).


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_usb` in the
Zephyr tree.

See :ref:`bluetooth setup section <bluetooth_setup>` for details.