From: Suraj Sumangala <suraj@Atheros.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Kevin Hayes <kevin@Atheros.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Marcel Holtmann <marcel@holtmann.org>,
"Henry Ptasinski" <henryp@broadcom.com>,
Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ?
Date: Thu, 14 Oct 2010 09:53:00 +0530 [thread overview]
Message-ID: <4CB685A4.8030301@Atheros.com> (raw)
In-Reply-To: <AANLkTik9oYwspVG4KFbMMq63SpBp++iZe=vxOSQhxRki@mail.gmail.com>
Hi Luis,
On 10/13/2010 11:39 PM, Luis R. Rodriguez wrote:
> Does HCI support uploading firmware? Can't we resolve this blacklist
> crap issue if devices just used HCI to upload firmware?
HCI does not support uploading firmware. But HCI does provide options
for vendor specific commands that can be used for uploading firmware as
long as your device has enough intelligence to understand the command
when it comes.
This is what we do for AR300x serial devices. We do not download
firmware, but we do download all configuration entries as VS HCI commands.
>
> Luis
Regards
Suraj
next prev parent reply other threads:[~2010-10-14 4:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 17:02 Firmware versioning best practices: ath3k-2.fw rename or replace ath3k-1.fw ? Luis R. Rodriguez
2010-10-08 17:27 ` Suraj Sumangala
2010-10-08 18:15 ` Luis R. Rodriguez
2010-10-08 22:47 ` Sven-Haegar Koch
2010-10-09 8:06 ` Marcel Holtmann
2010-10-12 21:17 ` Henry Ptasinski
2010-10-13 10:06 ` Marcel Holtmann
2010-10-13 17:42 ` Luis R. Rodriguez
2010-10-13 17:54 ` Kevin Hayes
2010-10-13 18:09 ` Luis R. Rodriguez
2010-10-13 18:41 ` Kevin Hayes
2010-10-14 4:23 ` Suraj Sumangala [this message]
2010-10-09 8:01 ` Marcel Holtmann
2010-10-11 7:14 ` Senthil Balasubramanian
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=4CB685A4.8030301@Atheros.com \
--to=suraj@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=dwmw2@infradead.org \
--cc=henryp@broadcom.com \
--cc=kevin@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@gmail.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).