From: Bob Miller <kbob@jogger-egg.engr.sgi.com>
To: linux-sound@vger.kernel.org
Subject: Driver Writer's Questions
Date: Tue, 16 Mar 1999 22:57:05 +0000 [thread overview]
Message-ID: <marc-linux-sound-92163226831993@msgid-missing> (raw)
Hi. I am trying to write a Linux sound driver. I have some questions
that I hope someone here can answer.
1. (the big question) This device requires a single DMA buffer of up
to 8 Kb in main memory. It reads/writes the buffer circularly. It
can't chain buffers. Can I use the OSS DMA routines to set that
up somehow (how?), or do I have to write a non-OSS driver?
What does this imply for mmap?
2. This device is capable of telling how many samples it has
read/written, with an accuracy of 1 sample. I'd like to export
that via the SNDCTL_DSP_GET{I,O}PTR, ioctls, but I can't see how
my driver can get control on those ioctls.
3. This device has memory-mapped registers. I want to write a probe
routine that can verify that the device is there at the address
it's supposed to be. Is there a Linux routine to "read memory and
trap any fault"?
4. The mixer doesn't have a capability that corresponds to
SOUND_MIXER_VOLUME. If I don't implement SOUND_MIXER_VOLUME, will
I be incompatible with 99% of the apps? If I have to, I can fake
it -- maintain a SW volume setting and merge it into the level
I send to all the other faders...
That's enough questions for now. Hopefully, these are easy for
someone who's familiar with the Linux sound architecture.
Thanks for any help.
K<bob>
next reply other threads:[~1999-03-16 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 22:57 Bob Miller [this message]
1999-03-17 10:38 ` Driver Writer's Questions Thomas Sailer
1999-03-17 14:33 ` Bob Miller
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=marc-linux-sound-92163226831993@msgid-missing \
--to=kbob@jogger-egg.engr.sgi.com \
--cc=linux-sound@vger.kernel.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 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.