From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: Shanmugamkamatchi Balashanmugam
<Shanmugamkamatchi.Balashanmugam@Atheros.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Deepak Dhamdhere <Deepak.Dhamdhere@Atheros.com>,
Sree Durbha <Sree.Durbha@Atheros.com>
Subject: RE: RFC: btusb firmware load help
Date: Thu, 07 Oct 2010 19:59:19 +0200 [thread overview]
Message-ID: <1286474359.20974.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1286465072.6145.151.camel@aeonflux>
On Thu, 2010-10-07 at 17:24 +0200, Marcel Holtmann wrote:
> I am still trying to figure out if this is one stage firmware loading or
> a two stage firmware loading. This is all pretty unclear and nobody has
> answered this clearly so far.
afaict, it's just one stage -- either it has sflash and you load ath3k
firmware over it (the problematic 3002-before-loading case), or it
doesn't have any firmware (and comes up with 3000) and you load the same
ath3k firmware over it with a different mechanism, which currently
announces itself as 3002 but can be changed.
johannes
next prev parent reply other threads:[~2010-10-07 17:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 23:07 RFC: btusb firmware load help Luis R. Rodriguez
2010-09-29 19:40 ` Luis R. Rodriguez
2010-10-05 8:23 ` Marcel Holtmann
2010-10-05 19:28 ` Luis R. Rodriguez
2010-10-05 19:58 ` Marcel Holtmann
2010-10-05 20:28 ` Luis R. Rodriguez
2010-10-05 21:50 ` Matthew Garrett
2010-10-06 7:09 ` Marcel Holtmann
2010-10-06 7:19 ` Marcel Holtmann
2010-10-06 15:26 ` Luis R. Rodriguez
2010-10-06 15:56 ` Marcel Holtmann
2010-10-06 16:38 ` Luis R. Rodriguez
2010-10-06 17:37 ` Luis R. Rodriguez
2010-10-06 17:39 ` Luis R. Rodriguez
2010-10-06 17:54 ` Johannes Berg
2010-10-06 18:22 ` Luis R. Rodriguez
2010-10-06 18:26 ` Luis R. Rodriguez
2010-10-06 18:28 ` Johannes Berg
2010-10-06 18:33 ` Luis R. Rodriguez
2010-10-07 15:09 ` Shanmugamkamatchi Balashanmugam
2010-10-07 15:15 ` Johannes Berg
2010-10-07 16:32 ` Bala Shanmugam
2010-10-07 17:57 ` Johannes Berg
2010-10-07 15:24 ` Marcel Holtmann
2010-10-07 16:33 ` Bala Shanmugam
2010-10-07 16:35 ` Bala Shanmugam
2010-10-07 16:42 ` Marcel Holtmann
2010-10-07 17:06 ` Bala Shanmugam
2010-10-08 8:24 ` Marcel Holtmann
2010-10-12 13:38 ` Kevin Hayes
2010-10-12 13:38 ` Kevin Hayes
2010-11-10 18:46 ` Luis R. Rodriguez
2010-11-10 18:32 ` Bala Shanmugam
2010-10-07 17:59 ` Johannes Berg [this message]
2010-10-08 8:26 ` Marcel Holtmann
2010-10-06 17:52 ` Sven-Haegar Koch
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=1286474359.20974.13.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Deepak.Dhamdhere@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
--cc=Sree.Durbha@Atheros.com \
--cc=holtmann@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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.