zephyr/samples/bluetooth/beacon/prj_nble.conf

CONFIG_BLUETOOTH=y
CONFIG_BLUETOOTH_CUSTOM=y
CONFIG_NBLE=y
CONFIG_BLUETOOTH_DEBUG_LOG=y
CONFIG_BLUETOOTH_DEVICE_NAME="Test beacon"
drivers: bluetooth: nble: restructures Bluetooth Kconfig options This moves both the Bluetooth HCI and NBLE drivers under "Bluetooth Drivers" category. This also adds a selection for choosing Bluetooth stacks as the bulk of both HCI and NBLE stacks cannot be compiled together. Note that this does not move the source files. That should be done in a separate change. Change-Id: I32fa7097ada0fdc52bcc745adb78c7273f4023c6 Signed-off-by: Daniel Leung <daniel.leung@intel.com> 2016-03-17 04:05:56 +08:00			`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_CUSTOM=y`
Bluetooth: beacon: Add support for testing with nble driver In addition to having a different CONF_FILE bt_enable needs to be given a callback since nble driver cannot block while initializing. Change-Id: I8bd2c79d0620e93dbecfef25c49c5529ff1ee954 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> 2016-01-20 22:55:51 +08:00			`CONFIG_NBLE=y`
Bluetooth: Add support for using SYS_LOG This add CONFIG_BLUETOOTH_DEBUG_LOG which depends on SYS_LOG since the later can actually use either CONFIG_PRINTK or CONFIG_STDOUT_CONSOLE. Change-Id: Ib2974d1331f6c91d119a218ec95e8bf01069377b Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> 2016-04-27 22:57:03 +08:00			`CONFIG_BLUETOOTH_DEBUG_LOG=y`
Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible Instead of using a hard-coded string, make the sample use the Kconfig variable for the device name. Change-Id: Ib09f594e1cba221f9064318572bd90d38bd2733a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> 2017-01-27 21:41:59 +08:00			`CONFIG_BLUETOOTH_DEVICE_NAME="Test beacon"`