From: Paco <paco@OhKeePa.Net>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64
Date: Fri, 19 Nov 1999 18:32:47 +0000 [thread overview]
Message-ID: <marc-linux-sound-94303660622511@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-91965172830159@msgid-missing>
On Fri, 19 Nov 1999, Heikki Kallasjoki wrote:
> On 18.11.99, at 23:29, Dave Mielke wrote with subject 'Re: AWE64':
> > (IO 0 (BASE 0x0620)) (IO 1 (BASE 0x0A20)) (IO 2 (BASE 0x0E20))
> ...
> > As you can see from tyhe above, REdHat's "sndconfig" utility did find all of
> > the ports just fine.
>
> Oh, that's great. At least it reduces the amounts of people I know who
> will ask me about this.
>
> As a comparison, the 'pnpdump' which came with the new Slackware-7.0
> didn't find the ports. ..RedHat seems to have done something to
> that. Thanks to them.
>
Actually, the "sndconfig" is not a RedHat utility at all. It's the
configuration tool that comes with the OSS sound drivers, and it *does*
recognize all the ports on the AWE64.
regards,
-Paco
SuSE6.2 w/ OSS-free drivers
next prev parent reply other threads:[~1999-11-19 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 2:37 AWE64 Conde Martinez Rodolfo
1999-02-22 4:24 ` AWE64 Conde Martinez Rodolfo
1999-02-22 21:20 ` AWE64 Keith Duthie
1999-11-18 22:06 ` AWE64 Dave Mielke
1999-11-18 22:38 ` AWE64 Heikki Kallasjoki
1999-11-19 4:29 ` AWE64 Dave Mielke
1999-11-19 14:53 ` AWE64 Heikki Kallasjoki
1999-11-19 18:32 ` Paco [this message]
1999-11-19 18:49 ` AWE64 Bill Nottingham
1999-11-19 18:57 ` AWE64 Paco
1999-11-19 18:58 ` AWE64 Paco
-- strict thread matches above, loose matches on Subject: below --
1999-11-18 21:20 AWE64 Great One
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-94303660622511@msgid-missing \
--to=paco@ohkeepa.net \
--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.