Date: Thu, 27 Jan 2005 13:23:27 +0100 From: Rainer Goellner <rainer@jabbe.de> To: Marcel Holtmann <marcel@holtmann.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: BlueFRITZ! USB v2.0 is not recognized Message-ID: <41F8DD3F.9020209@jabbe.de> In-Reply-To: <1106821788.28444.68.camel@pegasus> References: <41F8B429.8010504@jabbe.de> <1106821788.28444.68.camel@pegasus>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Holtmann wrote:
>
>>I'm failing to get my new AVM BlueFRITZ! v2.0 Bluetooth
>>dongle recognized on a fresh FreeBSD 5.3 installation.
>>This version of the BlueFRITZ! should be H:2 compliant,
>>but all I get is a ugen, no ubt.
>>
> ...
> the BlueFRITZ! USB v2.0 is a H:2 device, but it doesn't present itself
> with the Bluetooth device class. I suggest you add the vendor and
> product id to the driver like it is done for Linux.
>
Could you give me any hint where to look and where
to add the ids?
BTW, I almost forgot that I had changed USB_MATH(ubt) in
sys/netgraph/bluetooth/drivers/utb/ng_ubt.c like this
very early during my awkward attempts:
...
Static struct usb_devno const ubt_ignored_devices[] = {
{ 0x057c, 0x3800,
0, 0 } /* This should be the last item in the list */
};
...
Static struct usb_devno const ubt_broken_devices[] = {
{ 0x057c, 0x3800,
0, 0 } /* This should be the last item in the list */
};
...
AFAIK 0x057c is the vendor id, 0x3800 the device id.
Hope that's not what you meant...
Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41F8DD3F.9020209>