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

Just wondering: is anyone interested in exploring alternative methods
for the pc speaker driver?

I've one idea, with some rudimentary code, thats been gathering dust for 
a while. It uses the real time clock for timing, along with udelay.  
It also has a (very) rudimentary soundcore interface. The only advantage 
it would have as an alternative to the existing driver is that the only 
kernel code it touches is in rtc.c, and then only to export a couple of 
functions.  If I understand correctly the objections to the current driver, 
this means it *might* have the potential to have an outside chance of getting 
slipped into the cannonical kernel distribution.

Disadvantage: it sucks up cpu cycles like a black hole. One would need
at least a 266 MHz processor, and even then not recommended on a heavily 
loaded machine.  Sound quality is not quite as good as existing driver, 
although I've gotten functional speech using rsynth, and can also tweak 
Maelstrom, eg, to get reasonable sound.

Any comments, discussion, helpful advice, would be much appreciated.
                                                 --Robert

             reply	other threads:[~1999-04-21 19:46 UTC|newest]

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

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-92472595425861@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