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