From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Marcel Holtmann <holtmann@linux.intel.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: Wed, 06 Oct 2010 20:28:17 +0200 [thread overview]
Message-ID: <1286389697.3655.401.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTi=o4Mc72NrNoALBdS3YHeY7RMyyAJPsCy=uW3+F@mail.gmail.com>
On Wed, 2010-10-06 at 11:26 -0700, Luis R. Rodriguez wrote:
> > Good idea, I forgot about possible firmware changes :) Lets see if our
> > team can do that. Thanks for all the feedback.
>
> Deepak a proof of concept test can involve simply hex-editing the
> ath3k-1.fw and replacing 0x3002 to 0x3003, then the above patch might
> work.
$ hd ath3k-1.fw
...
00000670 00 00 00 00 00 00 00 00 00 00 00 00 f3 0c 02 30 |...............0|
00000680 12 01 10 01 e0 01 01 40 f3 0c 02 30 01 00 00 00 |.......@...0....|
...
that looks a lot like the IDs right there, in little endian :-)
johannes
next prev parent reply other threads:[~2010-10-06 18:28 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 [this message]
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
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=1286389697.3655.401.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Deepak.Dhamdhere@atheros.com \
--cc=Luis.Rodriguez@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 \
--cc=lrodriguez@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 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.