From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 15:32:30 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2C9616A4CE for ; Mon, 10 Jan 2005 15:32:30 +0000 (GMT) Received: from psismtp8.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA8643D1D for ; Mon, 10 Jan 2005 15:32:29 +0000 (GMT) (envelope-from jjess@homeunix.com) Received: from zurich.homeunix.com ([62.87.73.194]) byIA3XTX00.8PJ for ; Mon, 10 Jan 2005 16:32:21 +0100 Received: from jjess by zurich.homeunix.com with local (Exim 4.42 (FreeBSD)) id 1Co1Vu-0000IF-3D for freebsd-bluetooth@freebsd.org; Mon, 10 Jan 2005 16:31:26 +0100 Date: Mon, 10 Jan 2005 16:31:25 +0100 From: Jes To: freebsd-bluetooth@freebsd.org Message-ID: <20050110163125.060d1e26@zurich.homeunix.com> In-Reply-To: <20050107223725.15a4554d@zurich.homeunix.com> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: Jes Subject: Re: [spam] Re: Motorola E1000 and obexapp 1.4.4 in server mode X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2005 15:32:31 -0000 On Fri, 7 Jan 2005 22:37:25 +0100 Jes wrote: > > > at this point i'm not sure who is at fault here. after reading the > spec > > i was not sure if *entire* rfcomm frame must fit into l2cap mtu, or > > segmentation is allowed. i need to re-read the spec and look at more > > dumps from different bluetooth devices. it seems to me that if l2cap > > channel was configured to use 132 bytes mtu then device should not > send > > larger packets, so my first impression is that the phone has a bug. > > > > as workaround you might want to try this: > > > > 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and > > change RFCOMM_DEFAULT_MTU from 127 to 667. > > > > 2) re-compile ng_btsocket module, i.e. > > > > # cd /sys/modules/netgraph/bluetooth/socket/ > > # make depend > > # make > > # make install > > > > 3) reboot and try again > > > > No, it doesn't work nor obexapp in client mode with that change. It > really doesn't matter because of I can retrieve files from pc in > client > mode... > > > Thanks in deed Max > > Jes > -- The transfer initated from phone to Windows 2000 works fine, the same with a sony ericsson T610. The problem is "only" with obexapp. Maybe is a phone bug but could be possible to do a workaround to solve it ? Thx bye -- Ed Sullivan will be around as long as someone else has talent. -- Fred Allen