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