Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Thomas Sailer <sailer@ife.ee.ethz.ch>
To: linux-sound@vger.kernel.org
Subject: Re: Driver Writer's Questions
Date: Wed, 17 Mar 1999 10:38:48 +0000	[thread overview]
Message-ID: <marc-linux-sound-92169374607374@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92163226831993@msgid-missing>

Bob Miller wrote:
> 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?

If the device is not ISA, I wouldn't bother fitting it into the
OSS framework, a stand alone driver (like I did for some
PCI cards) is easier to do and more maitainable.

>    What does this imply for mmap?

That the DMA buffer mappable is 8k max. The mmap interface is
deprecated anyway. I've tried once to emulate the mmap interface
on top of read/write, but it never worked well, if you don't want
huge latencies.

> 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.

Take a look at eg. the es1370 driver

> 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

Unlikely

Tom

  reply	other threads:[~1999-03-17 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-16 22:57 Driver Writer's Questions Bob Miller
1999-03-17 10:38 ` Thomas Sailer [this message]
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-92169374607374@msgid-missing \
    --to=sailer@ife.ee.ethz.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox