From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: OSS emulation improvements.
Date: Thu, 05 Jan 2006 20:02:49 +0000 [thread overview]
Message-ID: <43BD7B69.7030103@superbug.demon.co.uk> (raw)
Hi,
I have be trying to think of ways to improve OSS emulation for ALSA.
Now, the ideal solution is probably a userland daemon that will create
kernel /dev/dspX nodes.
Any application opening/ioctl/read/write to /dev/dspX would have all
those calls redirected to the userland daemon.
But I am not exactly sure how to achieve this.
Lets assume that we are able to get a userland daemon to creative a /dev
node. The OSS application opens/ioctl it. This results in function calls
to the userland daemon. The OSS application then does a write(). This
write will then contain a pointer to the frames the OSS application
wishes to write to the sound card. How can the daemon do a memcopy of
those frames to it's own address space?
Next the problem with DMA. the OSS application requests are DMA buffer
via the IOCTL. This would result is the buffer actually being in the
userland daemon's address space. How could the OSS application get write
access to the userland daemon'd address space?
If someone could kindly answer the questions above. I.e. explain how one
might do it in Linux. I would be happy to implement the userland daemon
and it would just work!
I think that if we could achieve this approach, all OSS would then work
seamlessly, so please help me.
James
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-05 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 20:02 James Courtier-Dutton [this message]
2006-01-05 23:27 ` OSS emulation improvements Ove Kaaven
2006-01-05 23:57 ` James Courtier-Dutton
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=43BD7B69.7030103@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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