From: Peter Leif Rasmussen <plr@cedara.com>
To: linux-sound@vger.kernel.org
Subject: Re: Missing 16bit DMA channel
Date: Tue, 18 Apr 2000 15:00:35 +0000 [thread overview]
Message-ID: <marc-linux-sound-95607403219156@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95606803212331@msgid-missing>
Dave Mielke wrote:
>
> [quoted lines by Peter Leif Rasmussen on April 18, 2000, at 09:52]
>
> >I found in my pile of stuff an ESS1868 soundcard, which should be very SB
> >compatible
>
> Check the comments at the top of "/usr/src/linux/drivers/sound/sb_ess.c". They
> seem to be saying that the second DMA option is called "dma16", but that it
> only specifies a 16-bit DMA if set to 5, and that all other values really refer
> to 8-bit DMAs.
>
Yes, I looked and I found in that file:
* Full duplex is enabled by specifying dma16. While the normal dma must
* be one of 0, 1 or 3, dma16 can be one of 0, 1, 3 or 5. DMA 5 is a 16 bit
* DMA channel, while the others are 8 bit..
As duplex is what I am looking for.
This comment (if still valid) seems to indicate that even a second 8bit DMA
channel will make the driver work in full duplex, and only if you really need
a 16bit DMA channel you can specify that. The documentation doesn't give any
indication of this, so thank you for pointing it out. I couldn't yesterday
make it work, though, but will try a little harder now knowing that this
card probably should work.
As ESS is closely wedded to SB why then can't a true SB card, eg. the
SB Vibra 16, be made to use the second 8bit DMA channel in duplex mode?
Thanks,
Peter
next prev parent reply other threads:[~2000-04-18 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 13:52 Missing 16bit DMA channel Peter Leif Rasmussen
2000-04-18 14:41 ` Dave Mielke
2000-04-18 15:00 ` Peter Leif Rasmussen [this message]
2000-04-19 2:37 ` Paul Laufer
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-95607403219156@msgid-missing \
--to=plr@cedara.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.