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 From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 18:11:48 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 21D3716A4CE for ; Mon, 10 Jan 2005 18:11:48 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9495943D3F for ; Mon, 10 Jan 2005 18:11:47 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j0AIBhGF025597; Mon, 10 Jan 2005 12:11:43 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 12:11:44 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 12:11:11 -0600 Message-ID: <41E2C546.10801@savvis.net> Date: Mon, 10 Jan 2005 10:11:18 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> <20050110163125.060d1e26@zurich.homeunix.com> In-Reply-To: <20050110163125.060d1e26@zurich.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Jan 2005 18:11:11.0766 (UTC) FILETIME=[C410EB60:01C4F73F] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org 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 18:11:48 -0000 Jes, >>> 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... hcidump please? > 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 > ? that is what i said - i'm not sure who at fault here. the problem really is in l2cap/rfcomm layer *not* in the opexapp. the phone sends packets that exceeds configured mtu, so the stack drops them. these packets never reach obexapp. btw, did you try to push files from t610 to freebsd? does it work? i have se t68i and it works just fine. max > > > Thx bye From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 20:06:25 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 386F816A4CE for ; Mon, 10 Jan 2005 20:06:25 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFBD943D45 for ; Mon, 10 Jan 2005 20:06:24 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j0AK68GF002203; Mon, 10 Jan 2005 14:06:08 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 14:06:02 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 14:05:53 -0600 Message-ID: <41E2E01C.2090003@savvis.net> Date: Mon, 10 Jan 2005 12:05:48 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> <20050110163125.060d1e26@zurich.homeunix.com> <41E2C546.10801@savvis.net> In-Reply-To: <41E2C546.10801@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Jan 2005 20:05:53.0808 (UTC) FILETIME=[CA153100:01C4F74F] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: 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 20:06:25 -0000 Jes, can i ask you to try something else? basically its the same change as before, but you need to adjust a couple more variables. 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and change #define RFCOMM_DEFAULT_MTU 127 to #define RFCOMM_DEFAULT_MTU 667 2) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and change #define NG_BTSOCKET_RFCOMM_SENDSPACE \ (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) #define NG_BTSOCKET_RFCOMM_RECVSPACE \ (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) to #define NG_BTSOCKET_RFCOMM_SENDSPACE \ (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) #define NG_BTSOCKET_RFCOMM_RECVSPACE \ (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) 3) re-compile ng_btsocket module, i.e. # cd /sys/modules/netgraph/bluetooth/socket/ # make depend # make # make install 4) reboot and try again >>>> 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... > > > hcidump please? > >> 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 >> ? > > > that is what i said - i'm not sure who at fault here. the problem really > is in l2cap/rfcomm layer *not* in the opexapp. the phone sends packets > that exceeds configured mtu, so the stack drops them. these packets > never reach obexapp. > > btw, did you try to push files from t610 to freebsd? does it work? i > have se t68i and it works just fine. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 20:20:51 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 934FB16A4CE for ; Mon, 10 Jan 2005 20:20:51 +0000 (GMT) Received: from psismtp7.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 026AE43D2D for ; Mon, 10 Jan 2005 20:20:50 +0000 (GMT) (envelope-from jjess@homeunix.com) Received: from zurich.homeunix.com ([212.166.255.76]) byIA4B6O01.SSX for ; Mon, 10 Jan 2005 21:20:48 +0100 Received: from jjess by zurich.homeunix.com with local (Exim 4.42 (FreeBSD)) id 1Co615-000LGp-Ee; Mon, 10 Jan 2005 21:19:55 +0100 Date: Mon, 10 Jan 2005 21:19:55 +0100 From: Jes To: Maksim Yevmenkin Message-ID: <20050110211955.555b4f1f@zurich.homeunix.com> In-Reply-To: <41E2E01C.2090003@savvis.net> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> <20050110163125.060d1e26@zurich.homeunix.com> <41E2C546.10801@savvis.net> <41E2E01C.2090003@savvis.net> 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 cc: freebsd-bluetooth@freebsd.org Subject: 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 20:20:51 -0000 On Mon, 10 Jan 2005 12:05:48 -0800 Maksim Yevmenkin wrote: > Jes, > > can i ask you to try something else? basically its the same change as > before, but you need to adjust a couple more variables. > > 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and > change > > #define RFCOMM_DEFAULT_MTU 127 > > to > > #define RFCOMM_DEFAULT_MTU 667 > > > 2) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and change > > #define NG_BTSOCKET_RFCOMM_SENDSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) > #define NG_BTSOCKET_RFCOMM_RECVSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) > > to > > #define NG_BTSOCKET_RFCOMM_SENDSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) > #define NG_BTSOCKET_RFCOMM_RECVSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) > > > 3) re-compile ng_btsocket module, i.e. > > # cd /sys/modules/netgraph/bluetooth/socket/ > # make depend > # make > # make install Hi Max: Of course, I'll try it when I find a little :) ... I hope such event will be tomorrow :). I'll try as well obex push from a sony ericsson z600 (T610 is not mine).... So... I'll tell you... -- Just about every computer on the market today runs Unix, except the Mac (and nobody cares about it). -- Bill Joy 6/21/85 From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 21:48:06 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 E81B116A4CE for ; Mon, 10 Jan 2005 21:48:06 +0000 (GMT) Received: from psismtp6.vodafone.es (back.vodafone.es [212.73.32.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id B573743D54 for ; Mon, 10 Jan 2005 21:48:05 +0000 (GMT) (envelope-from jjess@homeunix.com) Received: from zurich.homeunix.com ([212.166.165.150]) byIA4F7S00.5EE for ; Mon, 10 Jan 2005 22:47:52 +0100 Received: from jjess by zurich.homeunix.com with local (Exim 4.42 (FreeBSD)) id 1Co7IX-0000FY-LM; Mon, 10 Jan 2005 22:42:01 +0100 Date: Mon, 10 Jan 2005 22:42:01 +0100 From: Jes To: Maksim Yevmenkin Message-ID: <20050110224201.373ad571@zurich.homeunix.com> In-Reply-To: <41E2E01C.2090003@savvis.net> References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> <20050110163125.060d1e26@zurich.homeunix.com> <41E2C546.10801@savvis.net> <41E2E01C.2090003@savvis.net> 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 cc: freebsd-bluetooth@freebsd.org Subject: 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 21:48:07 -0000 On Mon, 10 Jan 2005 12:05:48 -0800 Maksim Yevmenkin wrote: > Jes, > > can i ask you to try something else? basically its the same change as > before, but you need to adjust a couple more variables. > > 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and > change > > #define RFCOMM_DEFAULT_MTU 127 > > to > > #define RFCOMM_DEFAULT_MTU 667 > > > 2) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file and change > > #define NG_BTSOCKET_RFCOMM_SENDSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) > #define NG_BTSOCKET_RFCOMM_RECVSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) > > to > > #define NG_BTSOCKET_RFCOMM_SENDSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) > #define NG_BTSOCKET_RFCOMM_RECVSPACE \ > (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) > > > 3) re-compile ng_btsocket module, i.e. > > # cd /sys/modules/netgraph/bluetooth/socket/ > # make depend > # make > # make install > > > 4) reboot and try again WoW ! now I get everything working ... Those changes are good, tested with both motorola e1000 and sony ericsson z600, obexapp in both server and client mode and rfcomm_pppd. Thanks a lot Max. Bye -- Love at first sight is one of the greatest labor-saving devices the world has ever seen. From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jan 10 22:22:45 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 85B4716A4CE for ; Mon, 10 Jan 2005 22:22:45 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A9B443D48 for ; Mon, 10 Jan 2005 22:22:45 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j0AMMLvh013386; Mon, 10 Jan 2005 16:22:21 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 16:22:19 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Jan 2005 16:22:14 -0600 Message-ID: <41E30011.2050005@savvis.net> Date: Mon, 10 Jan 2005 14:22:09 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> <41DECEA3.5080500@savvis.net> <20050107195406.0c76f42e@zurich.homeunix.com> <41DEE958.70403@savvis.net> <20050107223725.15a4554d@zurich.homeunix.com> <20050110163125.060d1e26@zurich.homeunix.com> <41E2C546.10801@savvis.net> <41E2E01C.2090003@savvis.net> <20050110224201.373ad571@zurich.homeunix.com> In-Reply-To: <20050110224201.373ad571@zurich.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Jan 2005 22:22:14.0691 (UTC) FILETIME=[D644DF30:01C4F762] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: 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 22:22:45 -0000 Jes, >> can i ask you to try something else? basically its the same change >> as before, but you need to adjust a couple more variables. >> >> 1) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file >> and change >> >> #define RFCOMM_DEFAULT_MTU 127 >> >> to >> >> #define RFCOMM_DEFAULT_MTU 667 >> >> >> 2) edit /sys/netgraph/bluetooth/include/ng_btsocket_rfcomm.h file >> and change >> >> #define NG_BTSOCKET_RFCOMM_SENDSPACE \ (RFCOMM_MAX_CREDITS * >> RFCOMM_DEFAULT_MTU * 10) #define NG_BTSOCKET_RFCOMM_RECVSPACE \ >> (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 10) >> >> to >> >> #define NG_BTSOCKET_RFCOMM_SENDSPACE \ (RFCOMM_MAX_CREDITS * >> RFCOMM_DEFAULT_MTU * 2) #define NG_BTSOCKET_RFCOMM_RECVSPACE \ >> (RFCOMM_MAX_CREDITS * RFCOMM_DEFAULT_MTU * 2) >> >> >> 3) re-compile ng_btsocket module, i.e. >> >> # cd /sys/modules/netgraph/bluetooth/socket/ # make depend # make # >> make install >> >> >> 4) reboot and try again > > > WoW ! now I get everything working ... Those changes are good, > tested with both motorola e1000 and sony ericsson z600, obexapp in > both server and client mode and rfcomm_pppd. thanks for trying this. i'm glad it works for you now. once again it sort of points finger back at the phone. i did not change any logic in my code. all i did is changed default mtu on *rfcomm* sessions to match default *l2cap* mtu. btw, rfcomm spec says default rfcomm mtu should be 127 bytes. i still did not find anything in the spec that says otherwise. right now i'm fairly convinced that there is something wrong in l2cap/rfcomm channel configuration process. what i do not know is who is at fault here. i need to have access to the phone in question. anyone willing to donate phone/money? :) just for the record here how the fix works - default l2cap mtu is 672 bytes - rfcomm packet header is 5 bytes so, assuming one rfcomm frame must fit entirely into one l2cap packet we get 672 - 5 = 667 default rfcomm mtu. the second change it just to ensure we do not reserve too much memory for socket's send and receive buffers. > Thanks a lot Max. thank you for your time and patience. max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 07:36:55 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 D483616A4CE for ; Wed, 12 Jan 2005 07:36:55 +0000 (GMT) Received: from mx1.wewitro.net (mx1.wewitro.net [82.96.83.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D6A943D64 for ; Wed, 12 Jan 2005 07:36:55 +0000 (GMT) (envelope-from rene@fantastici.de) Received: from localhost (localhost [127.0.0.1]) by mx1.wewitro.net (Postfix) with ESMTP id 84A08865C for ; Wed, 12 Jan 2005 08:36:53 +0100 (CET) Received: from mx1.wewitro.net ([82.96.83.62]) by localhost (mx1.wewitro.net [82.96.83.62]) (amavisd-new, port 10024) with LMTP id 00874-04-2 for ; Wed, 12 Jan 2005 08:36:52 +0100 (CET) Received: from webmail.wewitro.net (webmail.wewitro.net [82.96.83.65]) by mx1.wewitro.net (Postfix) with ESMTP id 2CA088706 for ; Wed, 12 Jan 2005 08:36:52 +0100 (CET) Received: from www-data by webmail.wewitro.net with local (Exim 3.35 #1 (Debian)) id 1Cod3k-0000QJ-00 for ; Wed, 12 Jan 2005 08:36:52 +0100 Received: from pD9E6A462.dip0.t-ipconnect.de (pD9E6A462.dip0.t-ipconnect.de [217.230.164.98]) by webmail.wewitro.net (IMP) with HTTP for ; Wed, 12 Jan 2005 08:36:51 +0100 Message-ID: <1105515411.41e4d393d2c5b@webmail.wewitro.net> Date: Wed, 12 Jan 2005 08:36:51 +0100 From: rene@fantastici.de To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 217.230.164.98 X-Virus-Scanned: by amavisd-maia-1.0.0-rc5 (Debian) at wewitro.net Subject: HID Proxy switching 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: Wed, 12 Jan 2005 07:36:55 -0000 Hi List, I own a D-Link DBT-120 REV3 which has the latest Apple Firmware loaded. This Device has the so called HID Proxy feature enabled, so if I activate the device under my FreeBSD Current only the HID Part is visible. Under Linux there is a tool hid2hci which is able to switch between the two modes. Now I ask if there is such a tool for FreeBSD? I'm not a great coder but have looked into the source for hid2hci but it seems it is to much depended on Linux USB / BT Stack to port it to FreeBSD. Are there any alternatives to make the device useable under FreeBSD? René -- ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 12:09:41 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 2041616A4CE for ; Wed, 12 Jan 2005 12:09:41 +0000 (GMT) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFAEA43D4C for ; Wed, 12 Jan 2005 12:09:39 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from pegasus (p3EE2CD1A.dip.t-dialin.net [62.226.205.26]) j0CCA6LL012978; Wed, 12 Jan 2005 13:10:06 +0100 From: Marcel Holtmann To: rene@fantastici.de In-Reply-To: <1105515411.41e4d393d2c5b@webmail.wewitro.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> Content-Type: text/plain Date: Wed, 12 Jan 2005 13:09:35 +0100 Message-Id: <1105531775.7961.46.camel@pegasus> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on coyote.holtmann.net X-Virus-Scanned: ClamAV 0.80/631/Wed Dec 15 15:01:14 2004 clamav-milter version 0.80j on coyote.holtmann.net X-Virus-Status: Clean cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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: Wed, 12 Jan 2005 12:09:41 -0000 Hi Rene, > I own a D-Link DBT-120 REV3 which has the latest Apple Firmware loaded. > This Device has the so called HID Proxy feature enabled, so if I activate > the device under my FreeBSD Current only the HID Part is visible. Under Linux > there is a tool hid2hci which is able to switch between the two modes. Now I ask > if there is such a tool for FreeBSD? > > I'm not a great coder but have looked into the source for hid2hci but it seems > it is to much depended on Linux USB / BT Stack to port it to FreeBSD. Are > there any alternatives to make the device useable under FreeBSD? actually there is no dependency on the Linux BT stack and for accessing the USB functions it uses libusb. However for switching the Logitech Bluetooth hub it uses some hiddev magic which is Linux specific. So if you rib out the Logitech stuff there should be no problem in running hid2hci under any operating system that has support for libusb. Regards Marcel From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 18:45:32 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 7A95F16A4CE for ; Wed, 12 Jan 2005 18:45:32 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 014EA43D1F for ; Wed, 12 Jan 2005 18:45:32 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])j0CIiirW000806; Wed, 12 Jan 2005 12:44:44 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 12:44:41 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 12:44:22 -0600 Message-ID: <41E57004.8070201@savvis.net> Date: Wed, 12 Jan 2005 10:44:20 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: rene@fantastici.de References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> In-Reply-To: <1105531775.7961.46.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jan 2005 18:44:22.0530 (UTC) FILETIME=[BB7AE620:01C4F8D6] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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: Wed, 12 Jan 2005 18:45:32 -0000 Rene, >> I own a D-Link DBT-120 REV3 which has the latest Apple Firmware >> loaded. This Device has the so called HID Proxy feature enabled, so >> if I activate the device under my FreeBSD Current only the HID Part >> is visible. Under Linux there is a tool hid2hci which is able to what driver attaches to the device? ugen(4), uhid(4) or other? can you tell what endpoints are available? hint: look in /var/log/messages and /dev. >> switch between the two modes. Now I ask if there is such a tool for >> FreeBSD? not right now. but we can write one :) >> I'm not a great coder but have looked into the source for hid2hci >> but it seems it is to much depended on Linux USB / BT Stack to >> port it to FreeBSD. Are there any alternatives to make the device >> useable under FreeBSD? it does not depend on linux bluetooth stack. i'm positive it can be done in freebsd. in non-logitech case all you need to do is send control message. please read ugen(4) man page - its a good start (in particular USB_DO_REQUEST). in logitech case you need to send hid report to the device. please read usb(3) and uhid(4) man page (in particular USB_SET_REPORT). if you are not feeling like hacking please send me information about your device, i.e. driver info and usb descriptors dump and i will try to hack something for you. > actually there is no dependency on the Linux BT stack and for > accessing the USB functions it uses libusb. However for switching the > Logitech Bluetooth hub it uses some hiddev magic which is Linux > specific. So if you rib out the Logitech stuff there should be no > problem in running hid2hci under any operating system that has > support for libusb. libusb is a freebsd port, which means hid2hci should also be a port. i see no reason it use libusb. base system has all required libraries. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 20:35:26 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 DE5EC16A4CE for ; Wed, 12 Jan 2005 20:35:26 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D21F43D2F for ; Wed, 12 Jan 2005 20:35:26 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j0CKYa0f010275; Wed, 12 Jan 2005 14:34:36 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 14:34:24 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 14:34:06 -0600 Message-ID: <41E589BB.1060702@savvis.net> Date: Wed, 12 Jan 2005 12:34:03 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <419B9EF8.2090401@savvis.net> <1103269957.974.7.camel@localhost> <41C32471.2050805@savvis.net> <866530fusa.fsf@kamino.rfc1149.org> <41DB1084.2090405@savvis.net> <1105261338.1126.6.camel@localhost> In-Reply-To: <1105261338.1126.6.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jan 2005 20:34:07.0062 (UTC) FILETIME=[102ABF60:01C4F8E6] X-ECS-MailScanner: No virus is found cc: bluetooth cc: Hiroyuki Aizu cc: Yann Berthier Subject: Re: Bluetooth mouse 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: Wed, 12 Jan 2005 20:35:27 -0000 Vladimir and Guys, please take a look at FreeBSD PR misc/76107. it includes the patch that fixes PSM problem. prize goes to Hiroyuki Aizu and the pointy hat goes to me :) i've committed the fix into -current and will MFC it to RELENG_5 in 1 day. thanks, max >> Hi Guys, >> >> sorry for the delay :) >> >> i've trying to troubleshoot the problem with Logitech MX900 >> bluetooth mouse (invalid psm for hid-interrupt channel) and have >> been looking at all dumps you guys sent to me. >> >> here is what i found so far. >> >> 1) according to the dumps the mouse advertises correct psm, i.e. >> 0x13 >> >> 2) bthidcontrol(8) _should_ work just fine, but it _does_not_. for >> whatever reason it gets wrong psm (0x25). >> >> let me just ask one more question: did you guys set any gcc >> optimization flags? anything that is *not* default? > > > no, nothing in make.conf, > > /usr/src/usr.sbin/bluetooth/bthidd$ make -V CFLAGS -O2 > -fno-strict-aliasing -pipe -I/usr/src/usr.sbin/bluetooth/bthidd -g > -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized > /usr/src/usr.sbin/bluetooth/bthidd$ > > >> bottom line: the problem can be either in bthidcontrol(8) or sdp(3) >> library. i can not reproduce the problem here, so would anyone >> consider giving me remote access to your box and mouse for a few >> hours/days? > > > Unfortunately it is my work notebook, and usually it connected behind > some firewall and there is no good way to enter from Internet here. > > Let I try to debug this problem. As I understand bthidcontrol Dump > should show valid psm (0x13). > > >> thanks, max > > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 21:04:03 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 23B1216A4CE for ; Wed, 12 Jan 2005 21:04:03 +0000 (GMT) Received: from mx1.wewitro.net (mx1.wewitro.net [82.96.83.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CD5943D3F for ; Wed, 12 Jan 2005 21:04:02 +0000 (GMT) (envelope-from rene@fantastici.de) Received: from localhost (localhost [127.0.0.1]) by mx1.wewitro.net (Postfix) with ESMTP id 5FF90900F; Wed, 12 Jan 2005 22:04:01 +0100 (CET) Received: from mx1.wewitro.net ([82.96.83.62]) by localhost (mx1.wewitro.net [82.96.83.62]) (amavisd-new, port 10024) with LMTP id 14100-04; Wed, 12 Jan 2005 22:03:59 +0100 (CET) Received: from [192.168.17.48] (pD9E83997.dip.t-dialin.net [217.232.57.151]) by mx1.wewitro.net (Postfix) with ESMTP id 608CB82AF; Wed, 12 Jan 2005 22:03:59 +0100 (CET) In-Reply-To: <41E57004.8070201@savvis.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_Scholz?= Date: Wed, 12 Jan 2005 22:03:57 +0100 To: Maksim Yevmenkin X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by amavisd-maia-1.0.0-rc5 (Debian) at wewitro.net cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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: Wed, 12 Jan 2005 21:04:03 -0000 Am 12.01.2005 um 19:44 Uhr schrieb Maksim Yevmenkin: [...] > what driver attaches to the device? ugen(4), uhid(4) or other? can you=20= > tell what endpoints are available? hint: look in /var/log/messages and=20= > /dev. > I had uhid, ums and ukbd compiled into my kernel, so ukbd und ums take=20= the device. Your hints were the right ones ;-) just compiled hid2hci.c with libusb,=20= changed the kernel to use uhid, ums and ukbd as modules so that ugen attached to=20 the device. Then I loaded ubt_ng and used hid2hci to switch the modes, hid2hci gave an=20 error "Switching device 0a12:1000 to HCI mode failed (Input/output error)" but the=20 switch was successfully done and voila ubt_ng found my bluetooh device. If I'd have a bt mouse and/or keyboard there might be some hassle to=20 load and unload the modules in the right order to use the hid or the hci part, but I have neither=20 of them so it's okay. So thank you and Marcel for giving me the right input and yes hid2hci.c=20= has no dependencies on the Linux USB stack. Ren=E9 -- =20 From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 13 00:26:31 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 7227B16A4CE for ; Thu, 13 Jan 2005 00:26:31 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC6CC43D1D for ; Thu, 13 Jan 2005 00:26:30 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j0D0PsLE026542; Wed, 12 Jan 2005 18:26:06 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 18:25:47 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Jan 2005 18:25:40 -0600 Message-ID: <41E5C005.1040506@savvis.net> Date: Wed, 12 Jan 2005 16:25:41 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ren=E9_Scholz?= References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> In-Reply-To: <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 13 Jan 2005 00:25:41.0024 (UTC) FILETIME=[699D1A00:01C4F906] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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: Thu, 13 Jan 2005 00:26:31 -0000 René, >> what driver attaches to the device? ugen(4), uhid(4) or other? can >> you tell what endpoints are available? hint: look in >> /var/log/messages and /dev. > > I had uhid, ums and ukbd compiled into my kernel, so ukbd und ums > take the device. Your hints were the right ones ;-) just compiled > hid2hci.c with libusb, changed the kernel to use uhid, ums and ukbd > as modules so that ugen attached to the device. Then I loaded ubt_ng > and used hid2hci to switch the modes, hid2hci gave an error > "Switching device 0a12:1000 to HCI mode failed (Input/output error)" > but the switch was successfully done and voila ubt_ng found my > bluetooh device. hmm... ok. does device stay in hci mode? or do you have to switch it every time after you re-connect it? > If I'd have a bt mouse and/or keyboard there might be some hassle to > load and unload the modules in the right order to use the hid or the > hci part, but I have neither of them so it's okay. it would be real hassle if you had wired usb keyboard :) > So thank you and Marcel for giving me the right input and yes > hid2hci.c has no dependencies on the Linux USB stack. i've got to get me one of these dongles :) so i can write bsd version of hid2hci. max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 13 06:08:00 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 6144816A4CE for ; Thu, 13 Jan 2005 06:08:00 +0000 (GMT) Received: from mx1.wewitro.net (mx1.wewitro.net [82.96.83.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6188843D39 for ; Thu, 13 Jan 2005 06:07:59 +0000 (GMT) (envelope-from rene@fantastici.de) Received: from localhost (localhost [127.0.0.1]) by mx1.wewitro.net (Postfix) with ESMTP id 4460690F8; Thu, 13 Jan 2005 07:07:58 +0100 (CET) Received: from mx1.wewitro.net ([82.96.83.62]) by localhost (mx1.wewitro.net [82.96.83.62]) (amavisd-new, port 10024) with LMTP id 22931-02-2; Thu, 13 Jan 2005 07:07:56 +0100 (CET) Received: from [192.168.17.48] (pD9E83E75.dip.t-dialin.net [217.232.62.117]) by mx1.wewitro.net (Postfix) with ESMTP id 12FF98C25; Thu, 13 Jan 2005 07:07:55 +0100 (CET) In-Reply-To: <41E5C005.1040506@savvis.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> <41E5C005.1040506@savvis.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <7746422F-6529-11D9-BFF9-000A95688814@fantastici.de> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_Scholz?= Date: Thu, 13 Jan 2005 07:07:55 +0100 To: Maksim Yevmenkin X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by amavisd-maia-1.0.0-rc5 (Debian) at wewitro.net cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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: Thu, 13 Jan 2005 06:08:00 -0000 Am 13.01.2005 um 1:25 Uhr schrieb Maksim Yevmenkin: > Ren=E9, > >>> what driver attaches to the device? ugen(4), uhid(4) or other? can >>> you tell what endpoints are available? hint: look in >>> /var/log/messages and /dev. >> I had uhid, ums and ukbd compiled into my kernel, so ukbd und ums >> take the device. Your hints were the right ones ;-) just compiled >> hid2hci.c with libusb, changed the kernel to use uhid, ums and ukbd >> as modules so that ugen attached to the device. Then I loaded ubt_ng >> and used hid2hci to switch the modes, hid2hci gave an error >> "Switching device 0a12:1000 to HCI mode failed (Input/output error)" >> but the switch was successfully done and voila ubt_ng found my >> bluetooh device. > > hmm... ok. does device stay in hci mode? or do you have to switch it=20= > every time after you re-connect it? No it doesn't stay in this mode, on every re-connect it is in hid mode=20= again. I'll try to write a usbd rule that execute hid2hci to do this automaticly each time the=20 device connects. > >> If I'd have a bt mouse and/or keyboard there might be some hassle to >> load and unload the modules in the right order to use the hid or the >> hci part, but I have neither of them so it's okay. > > it would be real hassle if you had wired usb keyboard :) ;-) That's true. > >> So thank you and Marcel for giving me the right input and yes >> hid2hci.c has no dependencies on the Linux USB stack. > > i've got to get me one of these dongles :) so i can write bsd version=20= > of hid2hci. > If I woudn't need it every day for my GPS communication I would send it=20= to you to play. Btw. these devices are becoming very cheap today. I've seen my model=20 for 22 Euros here in Germany. Ren=E9 -- =20 From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 13 09:48:20 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 89C7116A4CE for ; Thu, 13 Jan 2005 09:48:20 +0000 (GMT) Received: from smtp13.wxs.nl (smtp13.wxs.nl [195.121.6.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35A1243D5A for ; Thu, 13 Jan 2005 09:48:20 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from ronald.echteman.nl (ip51cdc5d2.speed.planet.nl [81.205.197.210])2004))freebsd-bluetooth@freebsd.org; Thu, 13 Jan 2005 10:36:52 +0100 (CET) Received: (qmail 5897 invoked from network); Thu, 13 Jan 2005 09:36:51 +0000 Received: from unknown (HELO laptop.thuis.klop.ws) (192.168.1.4) by ronald.echteman.nl with SMTP; Thu, 13 Jan 2005 09:36:51 +0000 Received: (qmail 879 invoked from network); Thu, 13 Jan 2005 09:36:49 +0000 Received: from localhost.thuis.klop.ws (HELO smtp.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; Thu, 13 Jan 2005 09:36:49 +0000 Date: Thu, 13 Jan 2005 10:36:47 +0100 From: Ronald Klop In-reply-to: <41DDC64F.7000904@savvis.net> To: Maksim Yevmenkin Message-id: MIME-version: 1.0 Content-type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 Content-transfer-encoding: 7BIT User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) References: <41DD82CE.5080502@savvis.net> <41DD9095.6010409@savvis.net> <41DD997C.90605@savvis.net> <41DDAD45.2070807@savvis.net> <41DDC64F.7000904@savvis.net> cc: freebsd-bluetooth@freebsd.org Subject: Re: ng_ubt with Broadcom BCM92035DGL 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: Thu, 13 Jan 2005 09:48:20 -0000 On Thu, 06 Jan 2005 15:14:23 -0800, Maksim Yevmenkin wrote: > Ronald Klop wrote: > >> I just found these in my /var/log/messages. >> ng_hci_process_command_complete: ubt0hci - HCI command failed, >> OGF=0x3, OCF=0x1a, status=0xc >> ng_hci_process_command_complete: ubt0hci - HCI command failed, >> OGF=0x3, OCF=0x3, status=0xc >> The first is about a 'write_scan_enable 3' and the last is a 'reset'. >> Maybe it is valuable info. > > well, these are exactly what we saw already. command complete hci event > has status code 0xc - command disallowed. nothing new. bummer. > one last question: device work in windows, right? can you look at > windows install and see if there are files that look like firmware? i.e. > something like BCM*.{hex|bin}? > > if there are such files and you are fill like hacking then perhaps you > could add device id to the ubtbcmfw(4), recompile and load it. and then > use bcmfw(8) to upload windows firmware files into the device. > > i have no idea if this will work. it could even damage the device, so > its up to you :) I don't have windows. And already returned the device to the store. Will by another one in the future. Ronald. -- Ronald Klop, Amsterdam, The Netherlands