From: Marcel Holtmann <marcel@holtmann.org>
To: Bala Shanmugam <sbalashanmugam@atheros.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC] Bluetooth: Add firmware load infrastructure for BT devices
Date: Tue, 06 Jul 2010 14:24:21 -0300 [thread overview]
Message-ID: <1278437061.2789.62.camel@localhost.localdomain> (raw)
In-Reply-To: <1278333422-10368-1-git-send-email-sbalashanmugam@atheros.com>
Hi Bala,
> Added support to load firmware to target RAM from Bluetooth USB transport
> driver. Each BT device vendor need to specify the product ID, firmware file,
> load and unload function. When the device is inserted, btusb will call
> appropriate firmware load function to load firmware to target RAM.
>
> This framework is needed for devices that are detected as BT devices when
> powered on and still require firmware to be downaloded.
we have discussed this a long time ago and the better approach would be
to create a setup stage for all HCI drivers. For example for special HCI
commands to set BD_ADDR and other details. Maybe also a firmware loading
stage should be used. Making this USB specific sounds pretty much wrong
to me at this point. At least SDIO might have similar issues.
The current approach looks more hackish than actually nicely integrated.
Regards
Marcel
next prev parent reply other threads:[~2010-07-06 17:24 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 [this message]
2010-07-06 20:29 ` Perelet, Oleg
2010-07-08 12:25 ` Shanmugamkamatchi Balashanmugam
2010-07-08 13:42 ` Marcel Holtmann
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=1278437061.2789.62.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=sbalashanmugam@atheros.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).