On Tue, Jan 30, 2007 at 02:19:24PM -0800, Roland Dreier wrote:
> > You mean the bcm43xx wireless driver that's been upstream for months?
>
> Sorry, yes. For some reason I thought it was blocked on the dscape
> merge but obviously I was wrong. So a reverse-engineered driver got
> upstream WAY FASTER than a driver where the vendor published specs and
> GPLed source.
>
> Why did that happen? I would argue that it was because way more
> people cared about the broadcom driver (since the chip was in apple
> laptops and the wrt54g among other things). That developer and user
> interest is more important than the info provided by the vendor.
That may be partially true. But the main reason is that the rt2x00
team chose to depend upon the heretofore unmergeable devicescape stack.
In contrast, the bcm43xx driver had a port for the ieee80211+softmac
stack that was ready for merge much earlier. This is more a result
of confusion in one area of kernel development than an indictment of
Linux drivers in general.
FWIW, we are closing-in on a merge for the devicescape stack.
(No, really!) So, hopefully wireless will soon cease to be such a
fertile ground for bad examples...
Thanks,
John
--
John W. Linville
[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
