From: "Iain Sandoe" <iain@sandoe.co.uk>
To: linuxppc-dev@lists.linuxppc.org
Subject: provision of "driver" type facilities from user-space
Date: Fri, 09 Mar 2001 18:15:03 +0000 [thread overview]
Message-ID: <20010309181506.CB5212F00E@apollo.valhalla.net> (raw)
hi list,
I want to put a layer in between user-space and a driver (dmasound).
The reason is - that I want to provide facilities (transparently) to
applications and these facilities cannot be (sensibly) placed in the driver
[e.g. rate conversion and so on].
In this case to make dmasound look like it can do "anything" and help
support (easily) apps that don't really bother to check for h/w capabilities
properly.
It isn't really the best solution to bloat each and every app with code to
do the job - some form of sharing seems to be the right way.
so solution 1:
provide a pseudo-oss interface via a library:
psuedo_oss_open(), pseudo_oss_read() .... etc. etc.
so app source is amended and then linked with a lib providing the
appropriate stuff in user-space...
not, probably, going to be popular...
solution 2:
??? is there a way of doing this without the apps being amended but _still_
making sure that code that belongs in user-space resides and is executed
there?
preferably allowing apps to think they are just talking to /dev/dsp
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-03-09 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 18:15 Iain Sandoe [this message]
2001-03-09 20:01 ` provision of "driver" type facilities from user-space Hollis R Blanchard
2001-03-10 5:31 ` Brad Boyer
-- strict thread matches above, loose matches on Subject: below --
2001-03-10 15:21 Iain Sandoe
2001-03-10 15:26 Iain Sandoe
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=20010309181506.CB5212F00E@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).