From owner-cvs-src@FreeBSD.ORG Fri Jan 14 18:14:51 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B4B916A4CE; Fri, 14 Jan 2005 18:14:51 +0000 (GMT) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 578E543D31; Fri, 14 Jan 2005 18:14:51 +0000 (GMT) (envelope-from emax@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id j0EIEpwL096955; Fri, 14 Jan 2005 18:14:51 GMT (envelope-from emax@repoman.freebsd.org) Received: (from emax@localhost) by repoman.freebsd.org (8.13.1/8.13.1/Submit) id j0EIEp3f096954; Fri, 14 Jan 2005 18:14:51 GMT (envelope-from emax) Message-Id: <200501141814.j0EIEp3f096954@repoman.freebsd.org> From: Maksim Yevmenkin Date: Fri, 14 Jan 2005 18:14:51 +0000 (UTC) To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org X-FreeBSD-CVS-Branch: RELENG_5 Subject: cvs commit: src/sys/netgraph/bluetooth/include ng_btsocket_rfcomm.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2005 18:14:51 -0000 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