From: Hauke Mehrtens <hauke@hauke-m.de>
To: b43-dev@lists.infradead.org
Subject: Switching to 4.174.64.19 firmware for G-PHY cards?
Date: Tue, 07 Dec 2010 20:21:24 +0100 [thread overview]
Message-ID: <4CFE8934.4060803@hauke-m.de> (raw)
In-Reply-To: <4CFE538A.10808@lwfinger.net>
On 12/07/2010 04:32 PM, Larry Finger wrote:
> On 12/07/2010 06:28 AM, Rafa? Mi?ecki wrote:
>> W dniu 7 grudnia 2010 13:21 u?ytkownik Rafa? Mi?ecki <zajec5@gmail.com> napisa?:
>>> Currently we tell ppl to use 4.150.10.5 for G-PHY and 4.174.64.19 for
>>> LP-PHY on our wiki page.
>>>
>>> Firmware files for G-PHY differ a little between there two versions,
>>> but did we actually get any problems reports?
>>>
>>> Can we drop 4.150.10.5 description?
>>
>> openSUSE 11.3 seems to download 4.174.64.19 only with it's script and
>> I didn't heard about any reports. One more point for dropping
>> 4.150.10.5?
>
> I pushed the patch to change openSUSE's script early in the beta testing for
> that release. I have heard no complaints either. I agree that 4.150.10.5 should
> be dropped.
We had serious issues with firmware version 4.174.64.19 in OpenWrt and
switched back to the old on as the default option. This issue afftected
mostly LP-PHY devices.
See the Bug report: https://dev.openwrt.org/ticket/6907 This was with
kernel 2.6.32 and compat-wireless from round about March to May 2010.
Stable means the old firmware version and experimental the new one in
the bug report.
Hauke
next prev parent reply other threads:[~2010-12-07 19:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 12:21 Switching to 4.174.64.19 firmware for G-PHY cards? Rafał Miłecki
2010-12-07 12:28 ` Rafał Miłecki
2010-12-07 15:32 ` Larry Finger
2010-12-07 19:21 ` Hauke Mehrtens [this message]
2011-03-01 13:33 ` Rafał Miłecki
2011-03-02 0:11 ` chris at martin.cc
2011-03-02 0:20 ` Rafał Miłecki
2011-03-02 3:30 ` chris at martin.cc
2011-03-02 9:58 ` Rafał Miłecki
2011-03-02 10:52 ` Rafał Miłecki
2011-03-02 11:22 ` Jonas Gorski
2011-03-02 12:20 ` chris at martin.cc
2011-03-02 22:00 ` Larry Finger
2011-03-02 23:02 ` chris at martin.cc
2011-03-03 4:43 ` chris at martin.cc
2011-03-03 7:58 ` Rafał Miłecki
2011-03-03 11:50 ` Rafał Miłecki
2011-03-03 23:49 ` chris at martin.cc
2011-03-07 12:35 ` Rafał Miłecki
2011-03-04 0:37 ` chris at martin.cc
2011-03-07 12:26 ` Rafał Miłecki
2011-03-08 1:12 ` chris at martin.cc
2011-03-07 13:12 ` Rafał Miłecki
2011-03-07 16:41 ` Rafał Miłecki
2011-03-08 1:25 ` chris at martin.cc
2011-03-08 13:26 ` Rafał Miłecki
2011-03-09 0:44 ` chris at martin.cc
2011-03-09 0:47 ` Rafał Miłecki
2011-03-09 0:47 ` chris at martin.cc
2011-03-03 4:55 ` chris at martin.cc
2011-03-02 23:00 ` chris at martin.cc
2011-03-02 12:14 ` chris at martin.cc
2011-03-02 13:12 ` Rafał Miłecki
2011-03-02 23:12 ` Jonas Gorski
2011-03-03 3:40 ` chris at martin.cc
2011-03-03 7:55 ` Rafał Miłecki
2011-03-03 15:52 ` Larry Finger
2011-03-03 5:34 ` chris at martin.cc
2011-03-03 4:23 ` chris at martin.cc
2011-03-02 10:08 ` Rafał Miłecki
2011-03-02 12:17 ` chris at martin.cc
2011-03-03 3:44 ` chris at martin.cc
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=4CFE8934.4060803@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=b43-dev@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.