You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Marcel Holtmann 98bcd08b5b [Bluetooth] Correct RFCOMM channel MTU for broken implementations ... Some Bluetooth RFCOMM implementations try to negotiate a bigger channel MTU than we can support for a particular session. The maximum MTU for a RFCOMM session is limited through the L2CAP layer. So if the other side proposes a channel MTU that is bigger than the underlying L2CAP MTU, we should reduce it to the L2CAP MTU of the session minus five bytes for the RFCOMM headers. Signed-off-by: Marcel Holtmann <marcel@holtmann.org>		19 years ago
..
bnep	…
cmtp	[Bluetooth] Remaining transitions to use kzalloc()	19 years ago
hidp	…
rfcomm	[Bluetooth] Correct RFCOMM channel MTU for broken implementations	19 years ago
Kconfig	Linux-2.6.12-rc2	20 years ago
Makefile	…
af_bluetooth.c	…
hci_conn.c	…
hci_core.c	…
hci_event.c	…
hci_sock.c	…
hci_sysfs.c	[Bluetooth] Use real devices for host controllers	19 years ago
l2cap.c	…
lib.c	…
sco.c	[Bluetooth] Remaining transitions to use kzalloc()	19 years ago