From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Shanmugamkamatchi Balashanmugam
<Shanmugamkamatchi.Balashanmugam@Atheros.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH] linux-firmware: Remove ath3k-2.fw
Date: Thu, 3 Feb 2011 09:46:22 -0800 [thread overview]
Message-ID: <20110203174622.GA1226@tux> (raw)
In-Reply-To: <4D4A60E1.3080000@atheros.com>
On Thu, Feb 03, 2011 at 12:01:37AM -0800, Shanmugamkamatchi Balashanmugam wrote:
> On 2/3/2011 1:13 PM, David Woodhouse wrote:
> > On Fri, 2011-01-28 at 15:03 +0530, Bala Shanmugam wrote:
> >> ath3k-2.fw is obsolete and not use by Atheros chipsets
> >> anymore.
> > Are you telling me that there is no extant hardware, and no old kernels,
> > which would use this? It was added to the linux-firmware tree and
> > *never* used?
> >
> Yes David, no older kernel uses this firmware.
> We thought to have new firmware file for newer versions but
> our driver patch was not accepted and we decided to
> have single firmware for this chipset [ath3k-1.fw].
>
To be clear, the patch for upstream to use that firmware was submitted IIRC but
never merged upstream... you merged the firmware first. By the time it came
time to push it again, I had asked WTF was in it, and asked for the patch to
get merged, but it was made clear by our team the APIs never changed so Marcel
suggested we just replace the firmware in linux-firmware instead of adding a
new firmware and patching the driver.
Apologies for any trouble.
Luis
next prev parent reply other threads:[~2011-02-03 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1296207208-4465-1-git-send-email-sbalashanmugam@atheros.com>
2011-02-03 6:28 ` [PATCH] linux-firmware: Remove ath3k-2.fw Bala Shanmugam
2011-02-03 7:43 ` David Woodhouse
2011-02-03 8:01 ` Bala Shanmugam
2011-02-03 17:46 ` Luis R. Rodriguez [this message]
2011-02-08 6:35 ` Bala Shanmugam
2011-03-01 6:38 ` Bala Shanmugam
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=20110203174622.GA1226@tux \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Shanmugamkamatchi.Balashanmugam@Atheros.com \
--cc=dwmw2@infradead.org \
--cc=linux-bluetooth@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).