From: James Courtier-Dutton <James@superbug.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: TODO list
Date: Fri, 26 May 2006 12:29:11 +0100 [thread overview]
Message-ID: <4476E687.10608@superbug.co.uk> (raw)
In-Reply-To: <s5hpsi1qc1h.wl%tiwai@suse.de>
Takashi Iwai wrote:
>> 7) Provide better OSS emulation support. E.g. redirect all access to
>> /dev/dsp into user space so it can use all the features of alsa-lib
>> without needing aoss. (aoss does not work if the application uses
>> dynamically linked audio driver plugins.
>>
>
> A dummy kernel driver just to translate syscalls to communication with
> a user daemon is the only possible workaround, IMO. This idea was
> denied once quite ago, but I don't see any other good way right now.
>
That is my thought as well. When I looked into the idea some time ago, I
concluded that is would be a rather large project, so I did not proceed
as I have other more important (for me) ALSA features.
Can a user space daemon create /dev files, so that the application calls
never actually reach kernel space?
If we can create such a pipe, that can forward
open/close/read/write/ioctl, that should be enough. We then have to
think about shared memory to look like DMA space to the application
using us.
>
> My additional wishes are:
>
> 8) Improve release engineering.
>
> 9) Better organized Web pages and BTS.
>
> 10) Build standard test suite and diagnosis tools.
>
>
The words "Under staffed" comes to mind. :-)
> Takashi
>
James
next prev parent reply other threads:[~2006-05-26 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 18:10 TODO list James Courtier-Dutton
2006-05-25 18:36 ` Lee Revell
2006-05-26 11:07 ` Takashi Iwai
2006-05-26 11:29 ` James Courtier-Dutton [this message]
2006-05-26 15:34 ` Takashi Iwai
2006-05-26 16:33 ` James Courtier-Dutton
2006-05-26 16:52 ` Takashi Iwai
2006-05-26 17:30 ` James Courtier-Dutton
2006-05-26 18:43 ` Takashi Iwai
2006-06-30 12:08 ` Johannes Berg
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=4476E687.10608@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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