From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: David Lloyd <dmlloyd@tds.net>
Cc: Jaroslav Kysela <perex@suse.cz>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: OSS API redirector
Date: Sun, 21 Mar 2004 22:53:10 +0000 [thread overview]
Message-ID: <405E1CD6.4030404@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.3503191408270.16085@tomservo.workpc.tds.net>
David Lloyd wrote:
> On Thu, 18 Mar 2004, James Courtier-Dutton wrote:
>
>
>>What is the conclusion regarding fopen/fclose/fwrite/fread. Can it be
>>done?
>
>
> I thought that one rather pie-in-the-sky idea might be to use a kernel
> module that made /dev/dsp, /dev/mixer, etc., and reflects back to a
> userspace ALSA sound server via another device. This way, it doesn't
> matter how the device is opened.
>
> Might be difficult to do though, especially when you get mmap and
> dma involved.
>
> Just a thought, anyway.
>
> - D
>
>
I thought of that, but with that you just get different problems.
E.g. dmix only works is all application wishing to play sound are run by
the same user. You would probably need some daemon to run the /dev/dsp,
and that user deamon would have to run under the same user as any native
alsa app.
Cheers
James
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-21 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 9:32 OSS API redirector Jaroslav Kysela
2004-03-18 14:12 ` James Courtier-Dutton
2004-03-18 21:37 ` David Lloyd
2004-03-21 22:53 ` James Courtier-Dutton [this message]
2004-03-22 9:27 ` Jaroslav Kysela
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=405E1CD6.4030404@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=dmlloyd@tds.net \
--cc=perex@suse.cz \
/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