Re: [Feature Wish] GGI in Linux 2.3
Marcus Meissner (email@example.com)
Fri, 16 Jan 1998 10:24:16 +0100 (MET)
In article <KETILfirstname.lastname@example.org> you write:
>Hmm...I was thinking along the lines of the old GGI argument of "sound
>drivers get into the kernel, so why not graphics?" (approximated and
>condensed for your convenience)
>Now, thinking about the GGI issues of: a KGI, which defines access to
>the hardware, and libGGI, which contains routines for using that access
>(correct me if I'm wrong on this). Shouldn't sound behave similarly?
>That is, a KSI which opens for accessing the audio hardware, and a
>libGSI (or whatever). I admit to not knowing about how the sound
>driver(s) is implemented in the kernel, but couldn't this allow stuff
>like multiple sound cards (``multi-mouthed'' systems)? Wouldn't it
>simplify the kernel, and move stuff into userspace?
>Am I totally lost at sea here?
The soundstuff already is at the lowest common determinator in the
kernel, so splitting it is probably not a good idea.
And it supports multiple soundcards already.
(Ok, the softoss stuff could probably be done using a Sequencer loopback