[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200802291105.35713.mb@bu3sch.de>
Date: Fri, 29 Feb 2008 11:05:35 +0100
From: Michael Buesch <mb@...sch.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Alexey Zaytsev <alexey.zaytsev@...il.com>,
Larry Finger <Larry.Finger@...inger.net>,
Stefano Brivio <stefano.brivio@...imi.it>,
Jeff Garzik <jgarzik@...ox.com>, Greg KH <greg@...ah.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25.
On Friday 29 February 2008 09:21:19 Andrew Morton wrote:
> On Sat, 23 Feb 2008 16:17:55 +0300 Alexey Zaytsev <alexey.zaytsev@...il.com> wrote:
>
> > Theese two patches fix a problem instroduced in Linux 2.6.24, and
> > still present in the current Linus' 2.6.25 tree.
> >
> > The bcm43xx Wifi driver won't work any more, if the b44 Ethernet
> > driver is enabled. This happens because the b44 driver
> > needlessly enables the b43_pci_bridge code, which claims
> > the same pci ids as the bcm43xx driver. The b43_pci_bridge
> > code is needed for the b43{legacy} drivers, but for the
> > b44, only the "ssb pci core" is needed.
>
> Hate to stick my head into this beehive, but...
>
> I have a patch queued (the-scheduled-bcm43xx-removal.patch) which
> will remove this driver from 2.6.26.
>
> Is that bad?
Not at all. The b43 driver from 2.6.26 will work. So there's
no reason to keep bcm43xx.
Alexey just tested a patch that backports the fix to 2.6.24 and it
works fine.
--
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists