On Fri, Dec 14, 2007 at 11:56:24AM +0100, Ingo Molnar wrote:
quoted text
> 
> * Michael Buesch <mb@bu3sch.de> wrote:

quoted text
> > Oh come on. b43 is more than a year old now. How long should we wait? 
> > Two or three? Forever?
> 
> possibly forever, if you dont get obvious regressions like "my wlan does 
> not work" (reported in this very thread), resolved. Pushing the blame to 
> udev (in a rather unfriendly way) wont give users a working system and 
> wont get you many new testers for the new driver either.

It is true that Michael can be a little unpleasant at times.
The colloquialism that comes to mind is that he "does not suffer fools
lightly".  Hopefully he will take your counseling to heart and learn
to be a bit more moderate in his tone.  FWIW, he is still young. :-)

That said, it is also true that the b43[legacy] driver[s] do a more
than adequate job of replacing the old bcm43xx driver provided that
one (re-)installs the proper firmware.  And I know of no other driver
that goes to more trouble to tell you how to get the proper firmware
installed than this one.

The bcm43xx driver will be added to the feature removal schedule
in 2.6.25.  Proper judgment will be used in deciding the actual date
of its removal.  In the meantime hopefully every distribution will
have or obtain a working udev configuration.  If things don't work
out as planned then we will re-evaluate.

Let's stop this now please.

John
-- 
John W. Linville
linville@tuxdriver.com
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/