Linux Sound subsystem development
 help / color / mirror / Atom feed
From: <rtlynch@aracnet.com>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Sat, 12 Sep 1998 19:54:21 +0000	[thread overview]
Message-ID: <marc-linux-sound-90563086317468@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>

I would like to work on this.  I've been running linux for a while now but
never have bothered with sound. The last time I compiled my kernel I
included sound as a module but haven't made time to play around with
getting the plug-n-prey to work.  This would be good experience for me as
well as force me to finish my system setup :->

I was thinking of just implementing the script with perl. (Seems easy
anough.)  Are there any common pit falls that anyone can think of?  

	- Rusty Lynch (rtlynch@aracnet.com)

On Sat, 12 Sep 1998, Hamish Moffatt wrote:

> On Fri, Sep 11, 1998 at 11:59:04AM -0700, Adam Wiggins wrote:
> > At the moment I think a little shell script which worked like xf86config
> > or even the kernel "make config" would be a big improvement.  Ie, it just
> > seds the pnpdump file and gives you options:
> > 
> > % pnpsetup
> > Detected: "Creative Labs PnP Sound Chip"
> > Use this device? (y/n) y
> > What IO base? (220, 240, 260, 280, 2A0, 300) 280
> > What IRQ? (5, 7, 9, 10, 11) 10
> 
> Actually, that does sound pretty cool. I might write it, unless
> someone else has more time than I do (not hard) or more interest than I do
> and wants to volunteer. I'll test it; I have PnP sound cards
> and modems here, although not in the same box.
> 
> 
> Hamish
> 

  parent reply	other threads:[~1998-09-12 19:54 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 [this message]
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
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-90563086317468@msgid-missing \
    --to=rtlynch@aracnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox