Lyle Zhu 76c072549d Bluetooth: Classic: L2CAP: Fix the FCS incorrect issue ... The FCS flag of TX direction is not set correctly if the FCS flag of RX direction is set. The issue could be found with following steps, Step 1, Local sends configuration request with ERET mode and FCS omitted. Step 2, Peer replies the configuration response without any errors. Step 3, Peer sends configuration request with ERET mode and NO FCS. Step 4, Local replies the configuration response without any errors. The FCS flag of TX is cleared incorrectly. The FCS should be enabled if any one side enables the FCS. Signed-off-by: Lyle Zhu <lyle.zhu@nxp.com>		2025-04-28 08:36:13 +02:00
..
audio	Bluetooth: CSIP: Fix ntf issue to clients on reboot	2025-04-25 14:04:37 +02:00
common	subsys/bluetooth: Misc native_posix cleanup	2025-03-12 02:27:36 +01:00
controller	Bluetooth: Controller: Fix window widening for parameter update	2025-04-25 15:56:04 +02:00
crypto	Bluetooth: crypto: add select PSA_WANT_ALG_ECB_NO_PADDING	2025-01-15 22:57:20 +01:00
host	Bluetooth: Classic: L2CAP: Fix the FCS incorrect issue	2025-04-28 08:36:13 +02:00
lib
mesh	bluetooth: mesh: keep scanner enabled if lpn has been disabled	2025-04-25 14:05:27 +02:00
services	bluetooth: rename _bt_gatt_ccc and clarify usage	2025-04-17 17:24:19 +02:00
CMakeLists.txt
Kconfig	bluetooth: host: Remove experimental flag from LE Connection Subrating	2025-03-17 13:57:03 +01:00
Kconfig.adv	Bluetooth: Host: Remove experimental label from PAwR	2025-03-14 17:56:18 +01:00
Kconfig.logging