From: James Courtier-Dutton <James@superbug.co.uk>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Olivier Galibert <galibert@pobox.com>,
Lee Revell <rlrevell@joe-job.com>, Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
perex@suse.cz, Olaf Hering <olh@suse.de>
Subject: Re: [Alsa-devel] OSS driver removal, 2nd round
Date: Sun, 02 Jul 2006 07:55:27 +0100 [thread overview]
Message-ID: <44A76DDF.4020307@superbug.co.uk> (raw)
In-Reply-To: <44A6279C.3000100@superbug.co.uk>
James Courtier-Dutton wrote:
> "Never" probably only means terribly long. :-)
>
There is in fact one implementation method that we would like to
implement, but currently we don't know how, so some input from people
from this list might be helpful.
There is an ALSA tool called aoss.
What this does is hook any calls the application does to
fopen/fwrite/fread/fclose/open/close/read/write/ioctl etc. and detects
any calls to open /dev/dsp and /dev/mixer and diverts them to use
alsa-lib. This therefore manages to divert the applications use of
/dev/dsp before it even reaches the kernel. This therefore gives the
application full use of all the alsa-lib features. So, for example,
4-channel output would work in this mode. But, and this is the bit we
need help with, if the application uses dlopen to dynamically open a
plugin, the plugin's calls to open/close/read/write etc. are not hooked,
so the application fails.
Is there any way to also hook the IO calls of dlopened plugins?
James
next prev parent reply other threads:[~2006-07-02 6:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:21 OSS driver removal, 2nd round Adrian Bunk
2006-06-30 15:48 ` Ralf Baechle
2006-06-30 16:13 ` [Alsa-devel] " James Courtier-Dutton
2006-06-30 16:31 ` Olivier Galibert
2006-06-30 21:29 ` Lee Revell
2006-06-30 21:34 ` Arjan van de Ven
2006-06-30 21:54 ` Lee Revell
2006-07-01 8:54 ` Jan Engelhardt
2006-07-01 13:54 ` Lee Revell
2006-07-01 22:51 ` Jan Engelhardt
[not found] ` <200607010042.15765.ismail@pardus.org.tr>
2006-06-30 21:56 ` Lee Revell
[not found] ` <200607010249.05140.ismail@pardus.org.tr>
2006-07-03 22:38 ` Bill Davidsen
2006-07-05 7:27 ` Stefan Smietanowski
2006-07-05 19:34 ` Lee Revell
2006-07-05 21:56 ` Alan Cox
2006-07-01 7:31 ` [Alsa-devel] " Olivier Galibert
2006-07-01 7:43 ` James Courtier-Dutton
2006-07-01 13:52 ` Lee Revell
2006-07-02 6:55 ` James Courtier-Dutton [this message]
2006-07-02 9:58 ` Jan Engelhardt
2006-07-02 15:28 ` Lee Revell
2006-07-02 21:08 ` Jan Engelhardt
2006-07-02 21:16 ` Lee Revell
2006-07-03 9:26 ` Jan Engelhardt
2006-07-05 7:29 ` Stefan Smietanowski
2006-07-01 9:26 ` Jaroslav Kysela
2006-07-01 16:01 ` Adrian Bunk
2006-07-01 23:12 ` Adrian Bunk
2006-07-03 11:52 ` Benjamin Herrenschmidt
2006-07-03 19:42 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44A76DDF.4020307@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=perex@suse.cz \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox