From: Marcel Holtmann <marcel@holtmann.org>
To: Shanmugamkamatchi Balashanmugam
<Shanmugamkamatchi.Balashanmugam@Atheros.com>
Cc: "Perelet, Oleg" <operelet@quicinc.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: RE: [RFC] Bluetooth: Add firmware load infrastructure for BT devices
Date: Thu, 08 Jul 2010 10:42:52 -0300 [thread overview]
Message-ID: <1278596572.10421.25.camel@localhost.localdomain> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C4850DB2A787C@CHEXMB-01.global.atheros.com>
Hi Bala,
> Firmware loading to target RAM needs to be done once when the device is inserted. Firmware loading will not be required every time
> the device goes from DOWN to UP. I think each HCI driver requires
> a separate firmware loading code as firmware loading is
> different for different interfaces. Please advice if my understanding is wrong.
>
> I initially thought of registration
> mechanism with btusb transport driver to load firmware, but before
> the device is inserted btusb will not be loaded and registering the
> firmware load function with btusb was not possible.
>
> Please advice alternate solution to load firmware from transport driver.
my advise would be to just build devices that change their USB VID/PID
after the firmware got loaded. That way it is easy to have a firmware
loading driver and just btusb for real operation. Why is it so hard to
build just simple hardware that would just work.
Regards
Marcel
next prev parent reply other threads:[~2010-07-08 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 12:37 [RFC] Bluetooth: Add firmware load infrastructure for BT devices Bala Shanmugam
2010-07-06 17:24 ` Marcel Holtmann
2010-07-06 20:29 ` Perelet, Oleg
2010-07-08 12:25 ` Shanmugamkamatchi Balashanmugam
2010-07-08 13:42 ` Marcel Holtmann [this message]
2010-07-12 6:31 ` Shanmugamkamatchi Balashanmugam
2010-07-12 12:50 ` Marcel Holtmann
2010-07-13 12:18 ` Shanmugamkamatchi Balashanmugam
2010-07-13 12:43 ` Marcel Holtmann
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=1278596572.10421.25.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=operelet@quicinc.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;
as well as URLs for NNTP newsgroup(s).