Whoever added Zephyr's prefer-later-defaults Kconfig patch originally didn't do the same for 'range's. Earlier ranges are still preferred. Swap the ranges on BT_RFCOMM_L2CAP_MTU to give the intended behavior. Fixes the following warning for tests/bluetooth/shell/prj_br.conf: warning: default value 200 on BT_RFCOMM_L2CAP_MTU (defined at subsys/bluetooth/host/Kconfig:508) clamped to 264 due to being outside the active range ([264, 32767]) Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| common | ||
| controller | ||
| host | ||
| shell | ||
| CMakeLists.txt | ||
| Kconfig | ||