From: Marcel Holtmann Date: Fri, 14 Jul 2006 09:42:12 +0000 (+0200) Subject: [Bluetooth] Correct RFCOMM channel MTU for broken implementations X-Git-Tag: v2.6.18-rc3~43 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=98bcd08b5bfe78c1c9bda5768aa081e0fe4fcc4f;p=pandora-kernel.git [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 --- Reading git-diff-tree failed