Bluetooth: samples: Fix PAwR samples to match board capabilities
These samples were enabled for an nRF board, even though there is no upstream support for the feature. Additionally the sample.yaml files were forcefully disabling any in-tree HCI drivers, making it impossible to use e.g. qemu with an external HCI controller. Simply remove the nRF board from the list, as well as the odd Kconfig HCI driver options. Signed-off-by: Johan Hedberg <johan.hedberg@gmail.com>
This commit is contained in:
parent
c68770eda8
commit
eddac27c4e
4 changed files with 4 additions and 20 deletions
|
|
@ -6,10 +6,6 @@ tests:
|
|||
platform_allow:
|
||||
- qemu_cortex_m3
|
||||
- qemu_x86
|
||||
- nrf52840dk/nrf52840
|
||||
tags: bluetooth
|
||||
integration_platforms:
|
||||
- nrf52840dk/nrf52840
|
||||
extra_configs:
|
||||
- CONFIG_BT_CTLR=n
|
||||
- CONFIG_BT_NO_DRIVER=y
|
||||
- qemu_cortex_m3
|
||||
|
|
|
|||
|
|
@ -6,10 +6,6 @@ tests:
|
|||
platform_allow:
|
||||
- qemu_cortex_m3
|
||||
- qemu_x86
|
||||
- nrf52840dk/nrf52840
|
||||
tags: bluetooth
|
||||
integration_platforms:
|
||||
- nrf52840dk/nrf52840
|
||||
extra_configs:
|
||||
- CONFIG_BT_CTLR=n
|
||||
- CONFIG_BT_NO_DRIVER=y
|
||||
- qemu_cortex_m3
|
||||
|
|
|
|||
|
|
@ -6,10 +6,6 @@ tests:
|
|||
platform_allow:
|
||||
- qemu_cortex_m3
|
||||
- qemu_x86
|
||||
- nrf52840dk/nrf52840
|
||||
tags: bluetooth
|
||||
integration_platforms:
|
||||
- nrf52840dk/nrf52840
|
||||
extra_configs:
|
||||
- CONFIG_BT_CTLR=n
|
||||
- CONFIG_BT_NO_DRIVER=y
|
||||
- qemu_cortex_m3
|
||||
|
|
|
|||
|
|
@ -6,10 +6,6 @@ tests:
|
|||
platform_allow:
|
||||
- qemu_cortex_m3
|
||||
- qemu_x86
|
||||
- nrf52840dk/nrf52840
|
||||
tags: bluetooth
|
||||
integration_platforms:
|
||||
- nrf52840dk/nrf52840
|
||||
extra_configs:
|
||||
- CONFIG_BT_CTLR=n
|
||||
- CONFIG_BT_NO_DRIVER=y
|
||||
- qemu_cortex_m3
|
||||
|
|
|
|||
Loading…
Reference in a new issue