public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jacob Schmude <jacobs@ncinter.net>
To: speakup@braille.uwo.ca
Cc: Speakup Distribution List <speakup@speech.braille.uwo.ca>
Subject: Re: sound advice needed
Date: Wed, 29 Mar 2000 19:39:39 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0003291938010.1146-100000@jscomputer> (raw)
In-Reply-To: <x74s9p1jhf.fsf@speech.braille.uwo.ca>

Hang on, I thought alsa had isapnp support. In fact, that was one of the
main reasons I started using ALSA, those darn isapnp tools were to hard
to configure. You configure alsa at compile-time like this:
./configure --with-isapnp=yes

You then have a module called "isapnp.o" which will detect your pnp card.


On 29 Mar 2000, Kirk Reiser wrote:

> Hi Chuck:  The awe-64 is fine.  If it is an isa device you will need
> to use isapnp to set the ports where you want them to live and then
> tell alsa in your modules.conf.  If it is a pci device then you won't
> need the isapnp stuff but you'll still need to set things other than
> the snd_port and stuff in the options line of your modules.conf.  I
> can tell you more once I know what type of interface it is.  It
> doesn't really give you that much of an advantage over the sb16
> though.
> 
>   Kirk
> 
> -- 
> 
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 



  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chuck Hallenbeck
 ` Kirk Reiser
   ` Jacob Schmude [this message]
 ` Kerry Hoath
   ` Chuck Hallenbeck
 ` Terry D. Cudney
 ` cpt.kirk
   ` kestrell
     ` cpt.kirk
       ` Chuck Hallenbeck
 ` Victor Tsaran

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=Pine.LNX.4.21.0003291938010.1146-100000@jscomputer \
    --to=jacobs@ncinter.net \
    --cc=speakup@braille.uwo.ca \
    --cc=speakup@speech.braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).