From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jul 17 06:57:02 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 91C3516A41C for ; Sun, 17 Jul 2005 06:57:02 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from natsmtp00.rzone.de (natsmtp00.rzone.de [81.169.145.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0363343D45 for ; Sun, 17 Jul 2005 06:57:01 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-218-156-163.dclient.hispeed.ch [80.218.156.163]) (authenticated bits=0) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j6H6uwSf017427; Sun, 17 Jul 2005 08:56:59 +0200 (MEST) Message-ID: <42DA013A.3050900@jabbe.de> Date: Sun, 17 Jul 2005 08:56:58 +0200 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050714 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2005 06:57:02 -0000 Hi there, Why was the AVM BlueFritz! USB adapter put into the list of ignored devices? As Marcel Holtmann pointed out to me some time ago, at least version 2.0 is H:2 standard compliant, except that it doesn't tell us. I used it quite some time with a patch like kern/76205. AFAIK earlier versions of the adapter are problematic. I don't know how to distinguish them, but to ignore all of them doesn't sound like a good idea to me. From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jul 17 21:55:06 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 B293B16A41C for ; Sun, 17 Jul 2005 21:55:06 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 551A143D46 for ; Sun, 17 Jul 2005 21:55:06 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta11.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050717215505.SRVV24042.mta11.adelphia.net@[192.168.1.254]>; Sun, 17 Jul 2005 17:55:05 -0400 Message-ID: <42DAD3C5.9060800@savvis.net> Date: Sun, 17 Jul 2005 14:55:17 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Goellner References: <42DA013A.3050900@jabbe.de> In-Reply-To: <42DA013A.3050900@jabbe.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2005 21:55:06 -0000 Rainer, > Why was the AVM BlueFritz! USB adapter put into the list > of ignored devices? As Marcel Holtmann pointed out to me > some time ago, at least version 2.0 is H:2 standard compliant, > except that it doesn't tell us. I used it quite some time > with a patch like kern/76205. i guess its my fault. i misunderstood the purpose of the patch in the pr. i was under impression that intention was to _prevent_ ng_ubt(4) from attaching to the adapter, not _force_ it to attach. > AFAIK earlier versions of the adapter are problematic. > I don't know how to distinguish them, but to ignore all > of them doesn't sound like a good idea to me. i have a report which clearly states that AVM BlueFritz! usb adapter does not work with ng_ubt(4). i also have a dump of all usb interfaces and endpoints that does not look like H:2 standard compliant. i'm pretty sure that at the time i saw special Linux driver for the device. i did not port it because i did not have the device. could you please obtain a dump from the device that shows all the interfaces, endpoints, etc. and send it to me? perhaps there is way to distinguish between working and non-working version of the adapter. in the mean time i should probably revert my changes and force ng_ubt(4) to attach to the adapter. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Sun Jul 17 22:43:27 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 0004616A41F for ; Sun, 17 Jul 2005 22:43:26 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from natfrord.rzone.de (natfrord.rzone.de [81.169.145.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D526B43D5E for ; Sun, 17 Jul 2005 22:43:25 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-218-156-163.dclient.hispeed.ch [80.218.156.163]) (authenticated bits=0) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j6HMhNVJ013752; Mon, 18 Jul 2005 00:43:24 +0200 (MEST) Message-ID: <42DADF0D.4070509@jabbe.de> Date: Mon, 18 Jul 2005 00:43:25 +0200 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050714 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> In-Reply-To: <42DAD3C5.9060800@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jul 2005 22:43:27 -0000 Maksim Yevmenkin wrote: > Rainer, > >> Why was the AVM BlueFritz! USB adapter put into the list >> of ignored devices? As Marcel Holtmann pointed out to me >> some time ago, at least version 2.0 is H:2 standard compliant, >> except that it doesn't tell us. I used it quite some time >> with a patch like kern/76205. > > > i guess its my fault. i misunderstood the purpose of the patch in the > pr. i was under impression that intention was to _prevent_ ng_ubt(4) > from attaching to the adapter, not _force_ it to attach. > Seems reasonable from your point of view. >> AFAIK earlier versions of the adapter are problematic. >> I don't know how to distinguish them, but to ignore all >> of them doesn't sound like a good idea to me. > > > i have a report which clearly states that AVM BlueFritz! usb adapter > does not work with ng_ubt(4). i also have a dump of all usb interfaces > and endpoints that does not look like H:2 standard compliant. i'm pretty > sure that at the time i saw special Linux driver for the device. i did > not port it because i did not have the device. > Sounds like a pre v2.0 BlueFritz!. I'm sure you know about this; anyway, it may be of some help: http://www.holtmann.org/linux/bluetooth/features.html > could you please obtain a dump from the device that shows all the > interfaces, endpoints, etc. and send it to me? perhaps there is way to > distinguish between working and non-working version of the adapter. > How do I get that dump? Probably you don't just mean those few dmesg lines, do you? ubt0: Bluetooth Device Bluetooth Device, rev 1.10/15.00, addr 2 ubt0: Bluetooth Device Bluetooth Device, rev 1.10/15.00, addr 2 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; \ wMaxPacketSize=49; nframes=6, buffer size=294 > in the mean time i should probably revert my changes and force ng_ubt(4) > to attach to the adapter. > As an alternative, what would be a reasonable place to document the problem so that a user can find it? Thanks, Rainer From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jul 18 02:17:31 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 1743716A41C for ; Mon, 18 Jul 2005 02:17:31 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A497243D45 for ; Mon, 18 Jul 2005 02:17:30 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050718021730.BML29002.mta9.adelphia.net@[192.168.1.254]>; Sun, 17 Jul 2005 22:17:30 -0400 Message-ID: <42DB1141.1050008@savvis.net> Date: Sun, 17 Jul 2005 19:17:37 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Goellner References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> <42DADF0D.4070509@jabbe.de> In-Reply-To: <42DADF0D.4070509@jabbe.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 02:17:31 -0000 Rainer, [...] >> i have a report which clearly states that AVM BlueFritz! usb adapter >> does not work with ng_ubt(4). i also have a dump of all usb interfaces >> and endpoints that does not look like H:2 standard compliant. i'm >> pretty sure that at the time i saw special Linux driver for the >> device. i did not port it because i did not have the device. >> > Sounds like a pre v2.0 BlueFritz!. > > I'm sure you know about this; anyway, it may be of some help: > http://www.holtmann.org/linux/bluetooth/features.html yes, i've seen this page. however it has been awhile. i see it has been updated. thanks! >> could you please obtain a dump from the device that shows all the >> interfaces, endpoints, etc. and send it to me? perhaps there is way to >> distinguish between working and non-working version of the adapter. >> > How do I get that dump? Probably you don't just mean those > few dmesg lines, do you? not exactly. you needs to install udesc_dump (from ports/sysutils/udesc_dump). then have ugen(4) attached to the device (do not load ng_ubt(4)) and run udesc_dump on ugen device. i do not recall exact options to udesc_dump but it should be easy. i would like to get all descriptors, strings etc. as detail as you could get. > ubt0: Bluetooth Device Bluetooth Device, rev 1.10/15.00, addr 2 > ubt0: Bluetooth Device Bluetooth Device, rev 1.10/15.00, addr 2 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; \ > wMaxPacketSize=49; nframes=6, buffer size=294 that good to know too. >> in the mean time i should probably revert my changes and force >> ng_ubt(4) to attach to the adapter. >> > As an alternative, what would be a reasonable place to document > the problem so that a user can find it? ng_ubt(4) man page and/or bluetooth chapter in the handbook. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jul 18 07:55:38 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 A71BA16A41C for ; Mon, 18 Jul 2005 07:55:38 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from mail.holtmann.net (coyote.holtmann.net [217.160.111.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CDED43D49 for ; Mon, 18 Jul 2005 07:55:36 +0000 (GMT) (envelope-from marcel@holtmann.org) Received: from pegasus (p5487E426.dip.t-dialin.net [84.135.228.38]) by mail.holtmann.net (8.12.3/8.12.3/Debian-7.1) with ESMTP id j6I7wRXB018218 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 18 Jul 2005 09:58:28 +0200 From: Marcel Holtmann To: Maksim Yevmenkin In-Reply-To: <42DB1141.1050008@savvis.net> References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> <42DADF0D.4070509@jabbe.de> <42DB1141.1050008@savvis.net> Content-Type: text/plain Date: Mon, 18 Jul 2005 09:55:47 +0200 Message-Id: <1121673347.22662.52.camel@pegasus> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.85.1/982/Sun Jul 17 14:45:12 2005 on coyote.holtmann.net X-Virus-Status: Clean Cc: freebsd-bluetooth@freebsd.org, Rainer Goellner Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 07:55:38 -0000 Hi Maksim, > >> i have a report which clearly states that AVM BlueFritz! usb adapter > >> does not work with ng_ubt(4). i also have a dump of all usb interfaces > >> and endpoints that does not look like H:2 standard compliant. i'm > >> pretty sure that at the time i saw special Linux driver for the > >> device. i did not port it because i did not have the device. > >> > > Sounds like a pre v2.0 BlueFritz!. > > > > I'm sure you know about this; anyway, it may be of some help: > > http://www.holtmann.org/linux/bluetooth/features.html > > yes, i've seen this page. however it has been awhile. i see it has been > updated. thanks! there exists two AVM BlueFRITZ! dongles with different USB product ids: /* AVM BlueFRITZ! USB */ { USB_DEVICE(0x057c, 0x2200) }, /* AVM BlueFRITZ! USB v2.0 */ { USB_DEVICE(0x057c, 0x3800) }, The version 1.0 (with id 0x2200) needs a special driver and also a firmware download to work. The version 2.0 (with id 0x3800) is a standard H:2 dongle. They only didn't set the Bluetooth class for it. Regards Marcel From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jul 18 13:25:36 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 DC36F16A41C for ; Mon, 18 Jul 2005 13:25:36 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from natfrord.rzone.de (natfrord.rzone.de [81.169.145.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5716843D45 for ; Mon, 18 Jul 2005 13:25:36 +0000 (GMT) (envelope-from rainer@jabbe.de) Received: from [192.168.1.16] (80-218-156-163.dclient.hispeed.ch [80.218.156.163]) (authenticated bits=0) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id j6IDPYIa010655; Mon, 18 Jul 2005 15:25:34 +0200 (MEST) Message-ID: <42DBADCE.9090903@jabbe.de> Date: Mon, 18 Jul 2005 15:25:34 +0200 From: Rainer Goellner Organization: Arctopile User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050714 X-Accept-Language: de-de, de-ch, de, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> <42DADF0D.4070509@jabbe.de> <42DB1141.1050008@savvis.net> <1121673347.22662.52.camel@pegasus> In-Reply-To: <1121673347.22662.52.camel@pegasus> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 13:25:37 -0000 Marcel Holtmann wrote: > there exists two AVM BlueFRITZ! dongles with different USB product ids: > > /* AVM BlueFRITZ! USB */ > { USB_DEVICE(0x057c, 0x2200) }, > > /* AVM BlueFRITZ! USB v2.0 */ > { USB_DEVICE(0x057c, 0x3800) }, > > The version 1.0 (with id 0x2200) needs a special driver and also a > firmware download to work. The version 2.0 (with id 0x3800) is a > standard H:2 dongle. They only didn't set the Bluetooth class for it. > That's all we need! Thank you very much. So, Maksim, would you please put the first pair of lines into the array of ignored devices, the second one into the array of broken devices? And document that damn thing in ng_ubt(4)! Thanks, Rainer From owner-freebsd-bluetooth@FreeBSD.ORG Mon Jul 18 16:37:52 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 9981516A41C for ; Mon, 18 Jul 2005 16:37:52 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13AF843D45 for ; Mon, 18 Jul 2005 16:37:52 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 3689C3BE7C; Mon, 18 Jul 2005 11:37:51 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 10242-01-93; Mon, 18 Jul 2005 11:37:51 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id 046063BE6E; Mon, 18 Jul 2005 11:37:50 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 18 Jul 2005 11:37:45 -0500 Received: from [10.254.186.111] ([64.14.1.106]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 18 Jul 2005 11:37:42 -0500 Message-ID: <42DBDAD9.2070101@savvis.net> Date: Mon, 18 Jul 2005 09:37:45 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Goellner References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> <42DADF0D.4070509@jabbe.de> <42DB1141.1050008@savvis.net> <1121673347.22662.52.camel@pegasus> <42DBADCE.9090903@jabbe.de> In-Reply-To: <42DBADCE.9090903@jabbe.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Jul 2005 16:37:42.0155 (UTC) FILETIME=[048CF5B0:01C58BB7] X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: AVM BlueFritz! X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 16:37:52 -0000 Hello, >> there exists two AVM BlueFRITZ! dongles with different USB product ids: >> >> /* AVM BlueFRITZ! USB */ >> { USB_DEVICE(0x057c, 0x2200) }, >> >> /* AVM BlueFRITZ! USB v2.0 */ >> { USB_DEVICE(0x057c, 0x3800) }, >> >> The version 1.0 (with id 0x2200) needs a special driver and also a >> firmware download to work. The version 2.0 (with id 0x3800) is a >> standard H:2 dongle. They only didn't set the Bluetooth class for it. >> > That's all we need! Thank you very much. > > So, Maksim, would you please put the first pair of lines > into the array of ignored devices, the second one into > the array of broken devices? > > And document that damn thing in ng_ubt(4)! committed to -current. i will mfc it to releng_5/6 shortly. emax 2005-07-18 16:34:49 UTC FreeBSD src repository Modified files: sys/netgraph/bluetooth/drivers/ubt ng_ubt.c Log: Add support for AVM BlueFRITZ! USB Bluetooth Adapter v2.0. It appears that there are at least two versions of the adapter. Version 1 (product ID 0x2200) of the adapter does not work with ng_ubt(4) and require special driver and firmware. Version 2 (product ID 0x3800) seems to work just fine, except it does not have bDeviceClass, bDeviceSubClass and bDeviceProtocol set to required (by specification) values. This change forces ng_ubt(4) to attach to the version 2 adapter. Obtained from: Marcel Holtmann Submitted by: Rainer Goellner Revision Changes Path 1.24 +1 -1 src/sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jul 19 03:12:24 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 6DF0216A41C for ; Tue, 19 Jul 2005 03:12:24 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A37643D45 for ; Tue, 19 Jul 2005 03:12:23 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j6J3CNum020427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Jul 2005 20:12:23 -0700 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.8/Submit) id j6J3CNEc020425 for freebsd-bluetooth@freebsd.org; Mon, 18 Jul 2005 20:12:23 -0700 Date: Mon, 18 Jul 2005 20:12:23 -0700 From: "Loren M. Lang" To: freebsd-bluetooth@freebsd.org Message-ID: <20050719031223.GA20371@alzatex.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: Bluetooth Headset or Handsfree profile X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 03:12:24 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Has any work been done yet on implementing the Bluetooth Headset or Handsfree profiles in FreeBSD? I'd be quite interesting in helping to develop it. If I don't get any responces for a week, I might just start working on it from scratch. I believe the Headset profile is simplier, though it supports less features so I might start with that one. Also, I saw a mention that one reason FreeBSD doesn't support bluetooth audio yet is because the USB subsystem can't do isosynchronous transfers yet. Is this true? --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2 =20 --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC3G+XbTXoRwEYo9IRAiDfAJ0QYowos3TTIkj5B8bOkpLRCpu6IgCeNOyQ WzP4HkhMh1ujhUe58HRvaqY= =CV0t -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jul 19 03:39:21 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 26F6916A41F for ; Tue, 19 Jul 2005 03:39:21 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta13.adelphia.net (mta13.adelphia.net [68.168.78.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85E7843D49 for ; Tue, 19 Jul 2005 03:39:20 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta13.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with ESMTP id <20050719033918.HBQG14360.mta13.adelphia.net@[192.168.1.254]>; Mon, 18 Jul 2005 23:39:18 -0400 Message-ID: <42DC75F3.2000802@savvis.net> Date: Mon, 18 Jul 2005 20:39:31 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Loren M. Lang" References: <20050719031223.GA20371@alzatex.com> In-Reply-To: <20050719031223.GA20371@alzatex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Headset or Handsfree profile X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 03:39:21 -0000 Loren, > Has any work been done yet on implementing the Bluetooth Headset or > Handsfree profiles in FreeBSD? I'd be quite interesting in helping to > develop it. If I don't get any responces for a week, I might just start > working on it from scratch. I believe the Headset profile is simplier, > though it supports less features so I might start with that one. i have the sco support code in my local cvs. so far i managed to receive audio data from my plantronics m2500 headset with 3com usb bluetooth dongle. i will give it a little bit more polishing and testing and then commit it to -current. it probably would not make it to the 6.0 release. what exactly are you planning to implement and how exactly would you use headset and handsfree profiles on freebsd? > Also, I saw a mention that one reason FreeBSD doesn't support bluetooth > audio yet is because the USB subsystem can't do isosynchronous transfers > yet. Is this true? i never said freebsd can not do it. what i said is that i did not know how to do it. fortunately, i figured it all out. it is not very obvious, but after playing with it for awhile i managed to teach ng_ubt(4) to receive sco frames via isochronous transfers. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jul 21 15:52:41 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 2B5CD16A455 for ; Thu, 21 Jul 2005 15:52:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72F2443DFB for ; Thu, 21 Jul 2005 15:52:21 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j6LFqKXL066336 for ; Thu, 21 Jul 2005 10:52:20 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42DFC4B1.9010301@centtech.com> Date: Thu, 21 Jul 2005 10:52:17 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: bthidd causes panic on recent -current (7.0) X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2005 15:52:42 -0000 I recently cvsupped, and rebuilt world/kernel. After booting up, I panic when bthidd runs. It might be related to these options I added back into my kernel config: options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed options SMP # Symmetric MultiProcessor Kernel I have a dumpfile saved, if you want me to go through any debugging. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jul 21 16:16:11 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 2DD6016A422 for ; Thu, 21 Jul 2005 16:16:11 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C82643D5C for ; Thu, 21 Jul 2005 16:15:42 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 51B7A3BE4A; Thu, 21 Jul 2005 11:15:41 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26691-01-6; Thu, 21 Jul 2005 11:15:41 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id 2240D3BF12; Thu, 21 Jul 2005 11:15:41 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Jul 2005 11:15:32 -0500 Received: from [10.254.186.111] ([64.14.1.106]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Jul 2005 11:15:26 -0500 Message-ID: <42DFCA22.5080007@savvis.net> Date: Thu, 21 Jul 2005 09:15:30 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <42DFC4B1.9010301@centtech.com> In-Reply-To: <42DFC4B1.9010301@centtech.com> Content-Type: multipart/mixed; boundary="------------020404050306040302040702" X-OriginalArrivalTime: 21 Jul 2005 16:15:26.0350 (UTC) FILETIME=[67968AE0:01C58E0F] X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: bthidd causes panic on recent -current (7.0) X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2005 16:16:11 -0000 This is a multi-part message in MIME format. --------------020404050306040302040702 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Eric, > I recently cvsupped, and rebuilt world/kernel. After booting up, I > panic when bthidd runs. thanks for the report. the problem is not bthidd(8), its vkbd(4). i made a typo and did not properly initialize mutex (missed name). the patch is attached. thanks, max --------------020404050306040302040702 Content-Type: text/plain; name="vkbd.c.diff.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="vkbd.c.diff.txt" Index: vkbd.c =================================================================== RCS file: /usr/local/cvs/sys/dev/vkbd/vkbd.c,v retrieving revision 1.22 diff -u -r1.22 vkbd.c --- vkbd.c 23 Jun 2005 00:30:37 -0000 1.22 +++ vkbd.c 21 Jul 2005 16:11:15 -0000 @@ -65,7 +65,7 @@ *****************************************************************************/ #define VKBD_LOCK_DECL struct mtx ks_lock -#define VKBD_LOCK_INIT(s) mtx_init(&(s)->ks_lock, NULL, NULL, MTX_DEF) +#define VKBD_LOCK_INIT(s) mtx_init(&(s)->ks_lock, "vkbd_lock", NULL, MTX_DEF|MTX_RECURSE) #define VKBD_LOCK_DESTROY(s) mtx_destroy(&(s)->ks_lock) #define VKBD_LOCK(s) mtx_lock(&(s)->ks_lock) #define VKBD_UNLOCK(s) mtx_unlock(&(s)->ks_lock) --------------020404050306040302040702-- From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jul 21 16:27:07 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 234FA16A41F for ; Thu, 21 Jul 2005 16:27:07 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E391E43D5E for ; Thu, 21 Jul 2005 16:26:45 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j6LGQjbI067285; Thu, 21 Jul 2005 11:26:45 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42DFCCC2.7000603@centtech.com> Date: Thu, 21 Jul 2005 11:26:42 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maksim Yevmenkin References: <42DFC4B1.9010301@centtech.com> <42DFCA22.5080007@savvis.net> In-Reply-To: <42DFCA22.5080007@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: bthidd causes panic on recent -current (7.0) X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jul 2005 16:27:07 -0000 Maksim Yevmenkin wrote: > Eric, > >> I recently cvsupped, and rebuilt world/kernel. After booting up, I >> panic when bthidd runs. > > > thanks for the report. the problem is not bthidd(8), its vkbd(4). i made > a typo and did not properly initialize mutex (missed name). the patch is > attached. Yep, that does the trick! Thanks! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------