linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bala Shanmugam <sbalashanmugam@atheros.com>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: 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>,
	Deepak Dhamdhere <Deepak.Dhamdhere@Atheros.com>,
	Sree Durbha <Sree.Durbha@Atheros.com>
Subject: Re: RFC: btusb firmware load help
Date: Thu, 7 Oct 2010 22:03:59 +0530	[thread overview]
Message-ID: <4CADF677.8070506@atheros.com> (raw)
In-Reply-To: <1286465072.6145.151.camel@aeonflux>

  On 10/7/2010 8:54 PM, Marcel Holtmann wrote:
> Hi Bala,
>
>> Thanks Johannes.  This would be better option to change PID in firmware
>> as blacklisting 3002 might create problems for 3011 chipsets.
>> Will try and let you people know.
> The misbehaving 3002 needs to be blacklisted in btusb.c anyway. However
> after loading the firmware to 3002 device, it should change its PID to
> something else.
>
> 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.
>
> Regards
>
> Marcel
>
>
h

  reply	other threads:[~2010-10-07 16:33 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 [this message]
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=4CADF677.8070506@atheros.com \
    --to=sbalashanmugam@atheros.com \
    --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=johannes@sipsolutions.net \
    --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).