Date: Fri, 14 Jan 2005 18:14:51 +0000 (UTC) From: Maksim Yevmenkin <emax@FreeBSD.org> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/netgraph/bluetooth/include ng_btsocket_rfcomm.h Message-ID: <200501141814.j0EIEp3f096954@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
emax 2005-01-14 18:14:51 UTC
FreeBSD src repository
Modified files: (Branch: RELENG_5)
sys/netgraph/bluetooth/include ng_btsocket_rfcomm.h
Log:
MFC ng_btsocket_rfcomm.h v1.4 to RELENG_5
Make default RFCOMM session MTU match default L2CAP MTU.
This is just a workaround for a know problem with Motorola E1000
phone. Something is wrong with the configuration of L2CAP/RFCOMM
channel. Even though we set L2CAP MTU to 132 bytes (default RFCOMM
MTU 127 + 5 bytes RFCOMM frame header) and the phone accepts it,
the phone still sends oversized L2CAP packets. It appears that the
phone wants to use bigger (667 bytes) RFCOMM frames, but it does
not segment them according to the configured L2CAP MTU. The 667
bytes RFCOMM frame size corresponds to the default L2CAP MTU of
672 bytes (667 + 5 bytes RFCOMM frame header).
This problem only appears if connection was initiated from the
phone. I'm not sure who is at fault here, so for now just put
workaround in place. Quick look at the spec did not reveal any
anwser.
Revision Changes Path
1.2.4.1 +3 -3 src/sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501141814.j0EIEp3f096954>