Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Emil Stephan <ste@esqhen.su.eunet.de>
To: linux-sound@vger.kernel.org
Subject: Re: second dma
Date: Tue, 08 Sep 1998 20:17:05 +0000	[thread overview]
Message-ID: <marc-linux-sound-90532287605122@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90519114625121@msgid-missing>

Karsten Patzwaldt wrote:
> 
> hi!
> 
> when configuring the soundcard in the kernel-setup, the config-program
> tells me that i can choose whether i my card uses 5, 6 or 7 as 2nd
> dma-channel. but with my sb16-card, i have to use channel 1 there. it took
> me a long time to figure it out (maybe my way of figuring it out was too
> silly :) ), maybe this should be changed in future releases. i use 2.0.33,
> sorry if this is updated in 2.0.34 oder the 2.1.x-series.
> 
> and: what about a simple hardware-detection in the kernel-config? this is
> very off-topic, but this idea was born when i got angrier and angrier and
> then used pnpdump to get the dma and irq and so on of the card...
> 
> if there are any questions, please contact me directly, i'm not on this
> list...
> 
> ---
> Karsten Patzwaldt             http://kpa.notrix.de              kpa@gmx.net
>                         "Wisdom is earned... not given."
Hello Karsten,

i have an AWE64Gold, which shall be compatible to SB16 concerning the
audio
and midi part (Gold means gold plated in's and out's and cables, 64
means
32 soft synth voices plus 32 emu8000 voices, but the ISA-bus width is 16
as on the SB16). I use DMA 1 and 5 with this card. What thoughts led You
to the point, that You can use DMA 1 only ?

Bye, Emil.
-- 
--------------------------------------------------
Emil Stephan, Marktplatz 39, 53773 Hennef, Germany
voice: +49-2242-84438

Accelerate Windows: 9.81 m/sec^2 would be adequate

      reply	other threads:[~1998-09-08 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-07 17:26 second dma Karsten Patzwaldt
1998-09-08 20:17 ` Emil Stephan [this message]

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-90532287605122@msgid-missing \
    --to=ste@esqhen.su.eunet.de \
    --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