From: Matthew Garrett <mjg59@srcf.ucam.org>
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: Tue, 5 Oct 2010 22:50:08 +0100 [thread overview]
Message-ID: <20101005215008.GA11117@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTimz7U52_qHaTutQDOFQde+GrWJRA0WpqY__FPgi@mail.gmail.com>
On Tue, Oct 05, 2010 at 01:28:53PM -0700, Luis R. Rodriguez wrote:
> Right -- so ath3k depends on some atheros USB device IDs, and its a
> stupid driver that just loads firmware. The problem with this new
> device is that it requires two phases. One to load some sort of
> firmware onto it to get it to read as an ath3k device, and then ath3k
> will load the right firmware to it. So the hardware device is already
> claiming a btusb vendor:device ID, we can't change that I believe. Of
> course for future devices we can, and we've addressed this and its
> been fixed.
If the device IDs can be changed when the firmware is loaded, then
simply provide a driver that binds to the original IDs and uploads the
firmware. The original IDs can be blacklisted from btusb so it won't
interfere. The device will then boot the firmware, detach and reattach
with new IDs - btusb will then bind. Repeat for every cold reset.
If you can't change the IDs from firmware then an alternative would be
to blacklist it from btusb and provide a userspace application triggered
by a udev rule. Have it load the firmware and then poke
/sys/bus/usb/drivers/btusb/new_id .
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-10-05 21:50 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 [this message]
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
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=20101005215008.GA11117@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--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 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).