On Tuesday, 20 of November 2007, Michael Buesch wrote: > On Monday 19 November 2007 23:57:43 Rafael J. Wysocki wrote: > > > Having both drivers in 2.6.24 should help find out if > > > there's anything which should be ironed out with b43/b43legacy, but right > > > now they are already working a lot better than bcm43xx, and they are more > > > stable. So I couldn't find a reason why we shouldn't remove bcm43xx in > > > 2.6.25. > > > > Many people use the old driver and you are forcing them to switch in a > > rather > > unfriendly fashion. > > > > Moreover, the switch generally involves a configuration change (on my system > > eth1 became wlan0) and is not _that_ seamless. > > > > IMvHO, the schedule of the removal of this driver should be discussed on > > LKML. > > Ok, so we are going to add Rafael J. Wysocki as the bcm43xx maintainer > and remove everyone else. I'm OK with that.
[That wasn't nice.] I'm not qualified to maintain that code, sorry. Apart from this, I've switched to b43. :-) > It is known for over a year now that b43 (aka bcm43xx-mac80211) is going to > replace bcm43xx. And we already do a parrallel release cycle with both drivers > included so people can switch. What else do you want? _First_, mark bcm43xx as unmaintained. Then, it's not your problem any more. Perhaps there's someone who'd be willing to maintain it. Otherwise, it will be dropped anyway after some time - when no one uses it any more. Still, it need not be (and IMHO it shouldn't be) your decision to drop it. Greetings, Rafael _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
