Help¶

Use some heuristics to try to guess in advance whether the controller supports the HCI vendor extensions in advance, in order to prevent sending vendor commands to controller which may interpret them in completely different ways.

Direct dependencies¶

BT_HCI_VS_EXT && !BT_CTLR && BT_HCI && BT

(Includes any dependencies from ifs and menus.)

Default¶

y if BOARD_QEMU_X86 || BOARD_QEMU_CORTEX_M3 || BOARD_NATIVE_POSIX

Kconfig definition¶

At <Zephyr>/subsys/bluetooth/common/Kconfig:31

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:238

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Zephyr HCI Vendor-Specific Commands → Zephyr HCI Vendor-Specific Extensions

config BT_HCI_VS_EXT_DETECT
    bool "Use heuristics to guess HCI vendor extensions support in advance"
    default y if BOARD_QEMU_X86 || BOARD_QEMU_CORTEX_M3 || BOARD_NATIVE_POSIX
    depends on BT_HCI_VS_EXT && !BT_CTLR && BT_HCI && BT
    help
      Use some heuristics to try to guess in advance whether the controller
      supports the HCI vendor extensions in advance, in order to prevent
      sending vendor commands to controller which may interpret them in
      completely different ways.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)