From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Kevin Hayes <kevin@atheros.com>,
Deepak Dhamdhere <Deepak.Dhamdhere@atheros.com>,
Helen Chu <Helen.Chu@atheros.com>
Cc: Marcel Holtmann <holtmann@linux.intel.com>,
Shanmugamkamatchi Balashanmugam
<Shanmugamkamatchi.Balashanmugam@atheros.com>,
Luis Rodriguez <Luis.Rodriguez@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>,
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>,
Sree Durbha <Sree.Durbha@atheros.com>
Subject: Re: RFC: btusb firmware load help
Date: Wed, 10 Nov 2010 10:46:06 -0800 [thread overview]
Message-ID: <AANLkTikiST6OxNj2TN951s5Mh45ypgVi0bo=g0Hhkmaq@mail.gmail.com> (raw)
In-Reply-To: <B7132A25476D334D9130FE7532F2A56314B58158FF@SC1EXMB-MBCL.global.atheros.com>
On Tue, Oct 12, 2010 at 6:38 AM, Kevin Hayes <kevin@atheros.com> wrote:
> Yes, it is a good idea to let the downloadable firmware set a new PID, along with the
> blacklist on the 3002 PID for the first go round. I emphasize, it is the downloaded
> firmware that will be required to do the PID swizzling, not the sflash firmware. And I
> agree we should have a map of the PIDs in use and what they are used for, once
> we get through this immediate fixing phase.
FWIW, since we actually have customers already using this I took
Bala's original patch and put it into compat-wirelesss-2.6.36 and the
current bleeding edge compat-wireless so we can get customers at least
something working in the mean time. Of course this means we'll need to
support this patch should any issues come up ;).
The proper patch didn't make it to 2.6.37, hoping this will get
resolved for 2.6.38.
Luis
next prev parent reply other threads:[~2010-11-10 18:46 UTC|newest]
Thread overview: 35+ 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-11-10 18:46 ` Luis R. Rodriguez [this message]
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='AANLkTikiST6OxNj2TN951s5Mh45ypgVi0bo=g0Hhkmaq@mail.gmail.com' \
--to=mcgrof@gmail.com \
--cc=Deepak.Dhamdhere@atheros.com \
--cc=Helen.Chu@atheros.com \
--cc=Luis.Rodriguez@atheros.com \
--cc=Shanmugamkamatchi.Balashanmugam@atheros.com \
--cc=Sree.Durbha@atheros.com \
--cc=holtmann@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=kevin@atheros.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 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).