Re: [2.6 patch] schedule obsolete OSS drivers for removal

Florian Schmidt
2006-01-05T19:15:51Z

On Thu, 05 Jan 2006 13:36:20 -0500
Lee Revell <rlrevell@joe-job.com> wrote:

> OK so you can contrive an example. Have we ever seen a real world app
> where aoss can't work?

Well, until i provided my hacky and probably buggy patch to aoss to use
libc's fopen()-et. al.-hooks, no app using the OSS api by way of libc's
fopen() et. al. was able to use aoss. I don't use aoss anymore, as i
have hw mixing, so i haven't really done anymore testing. I admit of not
being sure, whether this principle error has any realistic impact (i.e.
apps/libs exist that resolve their system call symbols at build time - i
must also admit that i don't have really complete understanding of this
issue. maybe a more knowledgable person can speak up about possible use
scenarios besides libc).

> > Errm, i'm actually wrong about that. Kernel level OSS emu sw mixing
> > cannot work together with userspace ALSA sw mixing. I completely missed
> > that point.
> >
> > I still think, the easiest way would be to use FUSE as it gives the best
> > of both worlds:
>
> Yep, this does sound like a promising approach. AFAIK it's never been
> seriously explored as FUSE is so new.

Plus, i was wrong :) FUSE is for filesystems. fusd would be the choice
for this (not included in kernel yet). One might see how far one gets
with reusing code from both aoss and oss2jack

http://fort.xdas.com/~kor/oss2jack/

Btw: It has a nice list of compatible apps including skype and quake3
;)

Btw2: Heh, oss2jack already has direct ALSA support on its TODO list :)

fusd:

http://www.circlemud.org/%7Ejelson/software/fusd/

Regards,
Flo