Paul Barton-Davis hat gesagt: // Paul Barton-Davis wrote:
> yes, i think you will be quite free to do so. they won't work with
> ALSA API software, but thats OK for now.
What would that mean for aconnect? Could I (a)connect a
USB-midi-keyboard like the M-Audio Oxygen 8 with USB-midi to my SBLive
>>> But it does register itself to the OSS subsystem (to
>>> drivers/sound/sound_core.c) like all other sound drivers, so it _is_
>>> part of OSS.
>> no. sound_core is NOT part of OSS. ALSA attaches to it as well. Alan
>> Cox wrote that so that OSS and ALSA could (theoretically) co-exist.
>
>Now
On Thu, 17 Jan 2002, Paul Davis wrote:
>> But it does register itself to the OSS subsystem (to
>> drivers/sound/sound_core.c) like all other sound drivers, so it _is_
>> part of OSS.
> no. sound_core is NOT part of OSS. ALSA attaches to it as well. Alan
> Cox wrote that so that OSS and ALSA cou
>At least the driver handling the standard USB Audio Device Class is
>located in the USB kernel directory, ie. linux/drivers/usb. All code is in
>the big (~4000loc) audio.c file. It implements the OSS ioctls, plus
>OSS-style mmap() (and of course read()/write()).
>
>But it does register itself to
On Thu, 17 Jan 2002, Kai Vehmanen wrote:
[ ... w/ ALSA going to 2.5 kernel]
>>> What's going to happen with usb audio/midi support ?
> But it does register itself to the OSS subsystem (to
> drivers/sound/sound_core.c) like all other sound drivers, so it _is_ part
> of OSS. But basicly if ALSA pro
On Thu, 17 Jan 2002, Paul Davis wrote:
>> What's going to happen with usb audio/midi support ?
>> Since alsa should become the kernel standard driver for audio/midi/seq
>> devices and all the work the usb people have done to support the audio
>> class is based on the oss-api does that mean with 2
