From: Christian Lamparter <chunkeey@googlemail.com>
To: "Pekka Pietikäinen" <pp@ee.oulu.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [linux-firmware] Bump carl9170 1.9.6 -> 1.9.9?
Date: Fri, 28 Mar 2014 14:18:17 +0100 [thread overview]
Message-ID: <3136247.FK8ifUDRkI@debian64> (raw)
In-Reply-To: <53342374.7010602@ee.oulu.fi>
On Thursday, March 27, 2014 03:11:16 PM Pekka Pietikäinen wrote:
> linux-firmware seems to ship an oldish carl9170-1.fw, which seems to
> work ok except for spewing a lot of
>
> "[1889329.659407] ieee80211 phy0: invalid plcp cck rate (0)." messages.
In case of carl9170, these messages indicate that some non-802.11 transmitter
is near by (and confusing the chip a bit). These messages (and the associated
issues) can magically appear and disappear... So, chances are that they reappear
sometime later. There's little the firmware can do here.
> Grabbing 1.9.9 seems to make them go away and the driver works just as
> well :-)
>
> Any chance of someone bumping the version so the newer firmware gets
> shipped by distros?
Oh, I tried that back in October 2013.
<http://comments.gmane.org/gmane.linux.kernel.wireless.general/114639>
But no agreement has been reached. And 1.9.6 is good enough to download
the later firmware releases though. I'm sorry, but that's how it is at the moment.
But if you want to help, you could make a patch (the way Rick/Ben wants it) and
post it here (linux-wireless@vger.kernel.org). I can't do it, I tried and failed several
times. If you are interested: The firmware is under GPLv2, no sign-offs or acks
(from QCA, me or anyone else) is needed, you (or anyone else interested) can
go right ahead.
Regards,
Christian
prev parent reply other threads:[~2014-03-28 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 13:11 [linux-firmware] Bump carl9170 1.9.6 -> 1.9.9? Pekka Pietikäinen
2014-03-28 13:18 ` Christian Lamparter [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=3136247.FK8ifUDRkI@debian64 \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pp@ee.oulu.fi \
/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