Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Hamish Moffatt <moffatt@cs.rmit.edu.au>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Sat, 19 Sep 1998 12:59:42 +0000	[thread overview]
Message-ID: <marc-linux-sound-90620973826420@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>

On Mon, Sep 14, 1998 at 04:09:04PM -0400, Dave Wreski wrote:
> > > Guys, while I think this is a good idea, and something that surely can help a
> > > lot of people, perhaps your efforts would be better applied if you focused on
> > > the sndconfig utility that already has a moderately-working implementation.
> Check out:
> ftp://ftp.redhat.com/pub/sound/sndconfig
> 
> It seems to be able to probe your system for PnP sound cards.  Actually,
> I'm not sure if it's capable of probing for more than just SB cards.
> Also, I think it's configured to use the new sound modules available in
> the development kernels, and a patch to 2.0.35.

But that's sound configuration -- I think we are talking about
a generic PnP utility to handle sound, modems, network cards etc.
I certainly was.

Last time I looked at sndconfig (a while back) it did not use
the new sound modules, but some Redhat-specific sound modularization
patches. Hence it did not work for me on my Debian system; otherwise
we would probably have a Debian package of it.


Hamish
-- 
Hamish Moffatt, StudIEAust              hamish@debian.org, hamish@moffatt.nu
Student, computer science & computer systems engineering.    4th year, RMIT.
http://hamish.home.ml.org/ (PGP key here)             CPOM: [*******   ] 73%
"Note that in C++, as in life, friendship is not transitive" -- TC++3 manual

  parent reply	other threads:[~1998-09-19 12:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-07  3:18 AWE64 initial questions Dave Wreski
1998-09-08 20:06 ` Emil Stephan
1998-09-09  5:02 ` Dave Wreski
1998-09-09 14:39 ` Maddog Abel
1998-09-09 15:03 ` Juan Lupion
1998-09-09 19:40 ` Emil Stephan
1998-09-09 20:03 ` Dave Wreski
1998-09-09 21:03 ` Bill Nottingham
1998-09-09 22:13 ` Dan Hollis
1998-09-10  3:10 ` Dave Wreski
1998-09-10 16:23 ` Juan Lupion
1998-09-10 22:51 ` Dave Wreski
1998-09-10 23:22 ` Dan Hollis
1998-09-11  9:29 ` Hamish Moffatt
1998-09-11  9:31 ` Hamish Moffatt
1998-09-11 14:16 ` Dave Wreski
1998-09-11 18:59 ` Adam Wiggins
1998-09-12 10:11 ` Hamish Moffatt
1998-09-12 19:54 ` rtlynch
1998-09-13  0:51 ` Dave Wreski
1998-09-13  2:04 ` Jim
1998-09-13  2:11 ` llornkcor
1998-09-14 18:51 ` Adam Wiggins
1998-09-14 20:09 ` Dave Wreski
1998-09-15 15:14 ` rtlynch
1998-09-16  1:39 ` Bill Nottingham
1998-09-19 12:59 ` Hamish Moffatt [this message]
1998-09-19 13:01 ` Hamish Moffatt

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-90620973826420@msgid-missing \
    --to=moffatt@cs.rmit.edu.au \
    --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