From: "Jim" <aszure@gate.net>
To: linux-sound@vger.kernel.org
Subject: Re: AWE64 initial questions
Date: Sun, 13 Sep 1998 02:04:01 +0000 [thread overview]
Message-ID: <marc-linux-sound-90565208922896@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-90515879913606@msgid-missing>
For the sake of sounding rude...
But if we did that, and make it all simple like, wouldnt we then have
windoze?
-----Original Message-----
From: Dave Wreski <dave@nic.com>
To: rtlynch@aracnet.com <rtlynch@aracnet.com>
Cc: Linux Sound Mailing List <linux-sound@vger.rutgers.edu>; Linux Sound
Mailing List <linux-sound@vger.rutgers.edu>; Adam Wiggins <adam@angel.com>;
Hamish Moffatt <moffatt@cs.rmit.edu.au>
Date: Saturday, September 12, 1998 9:00 PM
Subject: Re: AWE64 initial questions
>
>On 12-Sep-98 rtlynch@aracnet.com wrote:
>> 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?
>
>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.
>
>Wouldn't it be better to start with the internals of sndconfig, port it to
your
>version of Linux, and resubmit the changes back to the maintainer of
sndconfig?
>
>Perhaps someone wants to make it gtk-capable, so we can have a graphical
means
>of controlling our PnP devices...
>
>Dave
>
next prev parent reply other threads:[~1998-09-13 2:04 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 [this message]
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-90565208922896@msgid-missing \
--to=aszure@gate.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.