linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bala Shanmugam <sbalashanmugam@atheros.com>
To: Shanmugamkamatchi Balashanmugam
	<Shanmugamkamatchi.Balashanmugam@Atheros.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ath3k-fw: Fix EEPROM radio table issue.
Date: Thu, 9 Dec 2010 17:31:09 +0530	[thread overview]
Message-ID: <4D00C505.7040500@atheros.com> (raw)
In-Reply-To: <1291367907-3650-1-git-send-email-sbalashanmugam@atheros.com>

On 12/3/2010 2:48 PM, Shanmugamkamatchi Balashanmugam wrote:
> Updated PID value to 3005 for devices with
> sflash firmware.
>
> Signed-off-by: Bala Shanmugam<sbalashanmugam@atheros.com>
> ---
>   WHENCE     |    2 ++
>   ath3k-1.fw |  Bin 246804 ->  246804 bytes
>   2 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/WHENCE b/WHENCE
> index 907fe68..0e3468f 100644
> --- a/WHENCE
> +++ b/WHENCE
> @@ -1101,6 +1101,8 @@ Driver: ath3k - DFU Driver for Atheros bluetooth chipset AR3011
>   File: ath3k-1.fw
>   Info: v1.0
>
> +Fix EEPROM radio table issue and change PID to 3005
> +
>   Licence: Redistributable. See LICENCE.atheros_firmware for details
>
>   --------------------------------------------------------------------------
> diff --git a/ath3k-1.fw b/ath3k-1.fw
> index 4a5ffb8de898fab1595662742f287493689e2b3b..63aa9b9ad87d3d918e441d921ada9cad08687ae5 100644
> GIT binary patch
> delta 129491
>
David,

We have upstreamed the transport driver changes.
We need this firmware upstreamed soon for our chip to work.

Do you have any comments on this patch?

Regards,
Bala.

      reply	other threads:[~2010-12-09 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  9:18 [PATCH] ath3k-fw: Fix EEPROM radio table issue Bala Shanmugam
2010-12-09 12:01 ` Bala Shanmugam [this message]

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=4D00C505.7040500@atheros.com \
    --to=sbalashanmugam@atheros.com \
    --cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@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).