From: Marcel Holtmann <marcel@holtmann.org>
To: "Raf D'Halleweyn" <list@noduck.net>
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: Sat, 21 Aug 2004 08:07:19 +0200 [thread overview]
Message-ID: <1093068439.3544.2.camel@notepaq> (raw)
In-Reply-To: <1093014039.28268.10.camel@base>
Hi Ralf,
> 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?
this is getting weird, because 0a12:0001 is a CSR based dongle and not a
Broadcom one. So firmware loading is not needed. It should simply work.
Give 2.6.8 a try.
Regards
Marcel
next prev parent reply other threads:[~2004-08-21 6:07 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
2004-08-21 6:07 ` Marcel Holtmann [this message]
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=1093068439.3544.2.camel@notepaq \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list@noduck.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.