Re: Distinguishing releases from pre-rc snapshots

[Pavel Roskin <proski@gnu.org>]

On Tue, 2007-10-16 at 22:41 -0400, Rik van Riel wrote:
> On Tue, 16 Oct 2007 22:22:43 -0400
> Pavel Roskin <proski@gnu.org> wrote:
> 
> > I'm trying to keep some external drivers up to date with the kernel,
> > and the first two weeks after the release is the worst time for me.
> 
> Consider this an incentive to submit your code for inclusion
> in the upstream kernel.  Having all the common drivers integrated
> in the mainline kernel makes it much easier for users to use all
> their hardware, external drivers are not just a pain for the developers.

The incentive has already worked for MadWifi, which has landed in the
wireless-2.6 repository under the name "ath5k".  Still, there is a lot
of work to do, and some features won't appear in the kernel driver soon,
partly because they rely on the chipset features that still need to be
reverse engineered.

In the meantime, somebody has to maintain the old madwifi and release
fixed for security and kernel compatibility.

Also, there are drivers that are just to unwieldy to be shaped into
something resembling a typical Linux driver.  linux-wlan-ng is such
project.  No matter what the incentive, it won't go to the kernel.
Maybe somebody will write a clean driver for Prism USB devices one day,
but it didn't happen so far.

Finally, there is a little at76_usb driver, which supports quite old
802.11b devices.  It's in wireless-2.6 as well, but I simply cannot
expect users to test it from there.  And if I make a standalone release,
I'd rather not make another one when 2.6.24 comes out.

-- 
Regards,
Pavel Roskin