Date: Sun, 17 Jul 2005 19:17:37 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Rainer Goellner <rainer@jabbe.de> Cc: freebsd-bluetooth@freebsd.org Subject: Re: AVM BlueFritz! Message-ID: <42DB1141.1050008@savvis.net> In-Reply-To: <42DADF0D.4070509@jabbe.de> References: <42DA013A.3050900@jabbe.de> <42DAD3C5.9060800@savvis.net> <42DADF0D.4070509@jabbe.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42DB1141.1050008>