Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Robert B. Hamilton" <rbh041a@unix.tamu.edu>
To: linux-sound@vger.kernel.org
Subject: Re: [RFD] Alternative PC speaker drivers?
Date: Fri, 23 Apr 1999 18:35:02 +0000	[thread overview]
Message-ID: <marc-linux-sound-92489349827822@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-92472595425861@msgid-missing>

> The PC speaker driver is a neat hack, but with the cost of low-end
> sound cards ($25-$30 in these parts for a SB16), I wonder if anyone
> would really use it.

Certainly that's true.  Still, people might find a use for it as
a "baseline" sound device (however crude) that is nearly guaranteed 
to be on every ix86 machine; and there is the occasional inquiry on l-k.
So perhaps there is no good reason not to support it, *provided* the 
support can be done in a technically acceptable manner.

Which brings us back to my original note.  Conventional wisdom has
had it that the maximum 8192Hz rate of the RTC is too low to support
the speaker driver.  I don't think that is true any more.  With faster
cpus one can use udelay's to get a finer time resolution (although
there are drawbacks).  If this is possible then it is a much cleaner 
solution than the current method which varies the system clock frequency.

But I've only tested this on my computer, a K6, so I don't know how well
it can work on others....I'd be willing to make the preliminary code 
available, and to work on midi, mixer and sequencer emulation, etc, if 
there were sufficient interest.....

----------------------------------------------------
Robert Hamilton
r-hamilton@physics.tamu.edu     

      parent reply	other threads:[~1999-04-23 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-21 19:46 [RFD] Alternative PC speaker drivers? Robert B. Hamilton
1999-04-21 23:57 ` Jeff Tranter
1999-04-23 18:35 ` Robert B. Hamilton [this message]

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-92489349827822@msgid-missing \
    --to=rbh041a@unix.tamu.edu \
    --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