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>		2006-07-24 12:44:25 -07:00
..
core.c	[Bluetooth] Correct RFCOMM channel MTU for broken implementations	2006-07-24 12:44:25 -07:00
Kconfig	Linux-2.6.12-rc2	2005-04-16 15:20:36 -07:00
Makefile	[Bluetooth] Move CRC table into RFCOMM core	2005-10-28 19:20:36 +02:00
sock.c	[Bluetooth] Use real devices for host controllers	2006-07-03 19:54:02 -07:00
tty.c	[Bluetooth] Remaining transitions to use kzalloc()	2006-07-12 15:34:28 -07:00