From: "Raf D'Halleweyn" <list@noduck.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1)
Date: Fri, 20 Aug 2004 11:00:39 -0400 [thread overview]
Message-ID: <1093014039.28268.10.camel@base> (raw)
In-Reply-To: <1092990717.18082.60.camel@pegasus>
On Fri, 2004-08-20 at 10:31 +0200, Marcel Holtmann wrote:
> your dongle looks like a Broadcom based dongle. Please include the part
> from /proc/bus/usb/devices matching your device. The main problem is
> that the mini driver and the firmware for the Broadcom dongle can't be
> loaded throught request_firmware() by the bcm203x driver. Check the
> BlueZ webpage for more details and put these files in the correct place.
>
> Regards
>
> Marcel
Okay, I had bluez-bluefw installed (Debian package) but it seems that
bluez now uses the standard firmware loading mechanism (request_firmware
()). As such, I copied the BCM2033-FW.bin and BCM2033-MD.hex files from
that package into /usr/lib/hotplug/firmware and removed bluez-bluefw.
However, I cannot find any evidence of the firmware actually being
loaded. I believe that my hotplug install is correctly installed (it can
load the ipw2100 firmware). I added some debugging
to /etc/hotplug/firmware.agent, but couldn't find any evidence of any
firmware being requested for the dongle.
Any suggestions what I could try next? Should I add USB_DEVICE(0x0a12,
0x0001) to the usb_device_id array in bcm203x.c?
BTW this used to work (but maybe this was under 2.4, using bluefw).
Raf.
/proc/bus/usb/devices for 1/19:
T: Bus=01 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#= 19 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 4.43
C:* #Ifs= 3 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
next prev parent reply other threads:[~2004-08-20 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 0:59 HCI USB on USB 2.0: hci_usb_intr_rx_submit (works with USB 1.1) Raf D'Halleweyn (list)
2004-08-09 11:01 ` Marcel Holtmann
2004-08-20 1:52 ` Raf D'Halleweyn (list)
2004-08-20 8:31 ` Marcel Holtmann
2004-08-20 15:00 ` Raf D'Halleweyn [this message]
2004-08-21 6:07 ` Marcel Holtmann
2004-08-30 19:05 ` Raf D'Halleweyn (list)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1093014039.28268.10.camel@base \
--to=list@noduck.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox