On Wed, Aug 4, 2010 at 6:26 AM, Ionuț Bîru <ibiru@archlinux.org> wrote:
On 08/04/2010 02:23 PM, Dan McGee wrote:
On Wed, Aug 4, 2010 at 1:03 AM, Ionuț Bîru<ibiru@archlinux.org> wrote:
On 08/04/2010 05:34 AM, Dan McGee wrote:
On Tue, Aug 3, 2010 at 9:24 PM, Dan McGee<dpmcgee@gmail.com> wrote:
On Tue, Aug 3, 2010 at 2:39 AM, Tobias Powalowski<t.powa@gmx.de> wrote:
Latest kernel is in testing, please signoff for both arches.
I already have .35 prepared, a fast signoff would be great.
This completely broke wireless for me on my laptop. b43 driver, i686 architecture. The wlan0 device would show up, but then you couldn't do much of anything with it.
03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) Subsystem: Hewlett-Packard Company Device 365e
Interesting, because the driver hasn't changed at all since the base 2.6.34 was released:
dmcgee@galway ~/projects/linux-2.6 (master) $ (find -name b43*) | xargs git diff v2.6.34..v2.6.34.2 | cat <no output here>
The diff on drivers/net/wireless didn't look odd either; specific (other) drivers changed but nothing that sticks out as affecting b43.
-Dan
it has ssb changes and b43 relies on it
Thanks, Ionuț. So much for a stable release...I should probably let them know upstream, no? Is this something to send to linux-stable?
-Dan
it was reported and we have a patch available
Awesome, good to see. It might be a pain in the ass but this is going to get reported again and again if we don't 1) build 2.6.34.3 when it comes out, hopefully soon or 2) Rebuild 2.6.34.2 with this patch. Loosing networking really sucks the big one. To Thomas: they are gong to have to given that this better end up in the next stable tree for that kernel. -Dan