> >- Writing a driver supporting every feature takes time - this is understood.
> > But there is no reason for delaying the release until that.
>
> I agree 100%.
>
> > I recommend going for the basic /dev/dsp (D/A A/D converters) first,
> > and release a beta as soon as that works. Then make new releases whenever
> > a new feature (midi, mixer, ...) is completed.
>
> That is traditionally the way the whole kernel has been built,
> no? All drivers start somewhere. Once part of a piece of
> hardware functions, it is immediately useful. Putting out a
> driver that supports part of a piece of hardware, while you
> continue to develop, means that it is being actively tested by
> the people with that hardware. If there are bugs, they will be
> found, and bug reports will start coming in. If the source code
> is available, then patches to fix the bugs will also come piling
> in. If the specs are available, then patches for the rest of the
> hardware's features will start pouring in as well.
That's right. Sombody ought to tell Creative (?) Labs & 4Front about
it...
--
Greetz,
Tygrys [161-Tango Delta Echo-002] - at 27MHz
if I have a bad day, ;-)
("`-''-/").___..--''"`-._ TyGrYs *** ExPeCt No MeRcY! ***
`6_ 6 ) `-. ( ).`-._-. KSS Network Administrator
(_Y_.)' ._ ) `._ `. "-..' http://www.tygrys.eu.org/
_..`--'_..-_/ /--'_.'_,' ICQ:3297597 LU156-NIC 2:484/53@fidonet
(((' (((-((('' (((( Linux Forever!!! Member of JTZ
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/