All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:33:39 +0100	[thread overview]
Message-ID: <44772DE3.60104@superbug.co.uk> (raw)
In-Reply-To: <s5hfyiwpzoe.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Fri, 26 May 2006 12:29:11 +0100,
> James Courtier-Dutton wrote:
>   
>> 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?
>>     
>
> No, only the kernel driver can handle certain syscalls like ioctl and
> mmap properly.  So, it must be a kernel driver that communicated with
> OSS apps (unless using LD_PRELOAD hack).
>
> The driver interprets each syscall to a certain protocol communicated
> with a dedicated daemon, and the daemon interprets it again to the
> real ALSA access.
>
>   
>> 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.
>>     
>
> mmap would be still tricky, maybe a kind of emulation via read/write.
>
>
> Takashi
>   

For mmap, all that happens is that the application asks for a mmap 
address from the kernel.
If we could get the kernel to manipulate shared memory, so that the mmap 
address given to the application is shared with the daemon, surely that 
would work.
Unfortunately, this might require some kernel memory manager modifications.
Shall I ask about this on the kernel mm list?

James

  reply	other threads:[~2006-05-26 16:33 UTC|newest]

Thread overview: 33+ 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
2006-05-26 15:34     ` Takashi Iwai
2006-05-26 16:33       ` James Courtier-Dutton [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-07-24  6:01 José Pekkarinen
2010-08-17 19:16 todo list varun satrawla
2010-07-14 10:01 TODO list Kulikov Vasiliy
2012-07-08 13:38 ` TODO List Benjamin BEURDOUCHE
2012-07-09  0:51 ` Keith Woodie
2015-04-03 20:40 ` TODO list Ravi Kerur
2015-04-07  7:49 ` Dan Carpenter
2015-04-09  0:36 ` Ravi Kerur
2015-04-09  8:48 ` Dan Carpenter
2015-04-09 22:57 ` Ravi Kerur
2015-04-10  5:34 ` Julia Lawall
2015-04-10 22:47 ` Ravi Kerur
2015-04-11  5:17 ` Julia Lawall
2015-04-13 22:02 ` Dan Carpenter
2015-04-13 22:42 ` Ravi Kerur
2015-04-14  6:58 ` Dan Carpenter
2009-11-21 16:30 todo list Krzysztof
2005-10-25  8:50 TODO List SMohideen
2005-10-30  9:44 ` Harald Welte
2000-04-28 11:52 Jamey Hicks
2000-04-28 12:17 ` Trevor Woolven
2000-04-29  0:27 ` David Woodhouse
2000-04-28  8:38 Trevor Woolven

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=44772DE3.60104@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.