From: Paulo Marques <pmarques@grupopie.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
David Schwartz <davids@webmaster.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: PC speaker
Date: Wed, 13 Jun 2007 11:41:38 +0100 [thread overview]
Message-ID: <466FC9E2.9060306@grupopie.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0706131119010.7198@blysk.ds.pg.gda.pl>
Maciej W. Rozycki wrote:
> On Tue, 12 Jun 2007, Jan Engelhardt wrote:
>
>>> 4) It assumes the current will be sufficient to burn out the speaker. (I
>>> know it will get very hot on older machines, whether it will burn out --
>>> might even depend on the exact speaker model.)
>> Since you can set the x86's crystals frequency from 1193182 to 18 Hz
>> (PIT_TICK_RATE / 1 to PIT_TICK_RATE / 65535) [*], you can never really
>> bust it. But even then, what would a speaker do it was constanly given
>
> I am fairly sure you have a choice between a steady low and a steady high
> level on the speaker output available if you switch the 8254 to the right
> single-shot mode. In case you have not been into such details -- the 8254
> offers six modes of operation, selected for each channel separately, of
> which only two are periodic.
Can we please stop this non-sense thread? Anyone designing the speaker
circuit would certainly place a small capacitor in series with the
speaker to kill the DC component of the signal.
Since the speaker itself wouldn't be able to play very low frequencies
anyway, the capacitor wouldn't have to be that big.
So I'm pretty sure that on any half-way decent piece of hardware, you
won't be able to kill the speaker with software...
--
Paulo Marques - www.grupopie.com
"Don't hit a man when he's down -- kick him; it's easier."
next prev parent reply other threads:[~2007-06-13 10:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 12:45 PC speaker R.F. Burns
2007-06-12 13:31 ` Jan Engelhardt
2007-06-12 13:54 ` R.F. Burns
2007-06-12 13:57 ` Jan Engelhardt
2007-06-12 15:09 ` Jan Engelhardt
2007-06-12 15:19 ` Alan Cox
2007-06-12 17:26 ` Jan Engelhardt
2007-06-12 20:08 ` David Schwartz
2007-06-12 20:34 ` Jan Engelhardt
2007-06-13 9:22 ` Helge Hafting
2007-06-13 10:27 ` Maciej W. Rozycki
2007-06-13 10:41 ` Paulo Marques [this message]
2007-06-13 19:53 ` Pavel Machek
2007-06-15 0:36 ` Kyle Moffett
2007-06-12 14:44 ` Lee Revell
2007-06-12 17:39 ` jimmy bahuleyan
2007-06-12 20:25 ` R.F. Burns
2007-06-12 20:36 ` Jan Engelhardt
2007-06-12 21:15 ` Clemens Koller
2007-06-12 22:08 ` David Schwartz
2007-06-13 12:26 ` Chris Smith
2007-06-15 17:07 ` Phillip Susi
2007-06-15 19:34 ` Jan Engelhardt
2007-06-15 23:30 ` Phillip Susi
2007-06-16 3:20 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 17:08 R.F. Burns
2008-07-08 17:38 ` Jan Engelhardt
2009-06-12 21:28 R.F. Burns
2009-06-12 21:40 ` Valdis.Kletnieks
2009-06-13 0:10 ` John Sheu
2010-06-12 21:32 R.F. Burns
2010-06-12 21:50 ` Daniel Hazelton
2010-06-13 0:07 ` Alan Cox
2016-08-05 16:51 R.F. Burns
2017-06-12 19:13 R.F. Burns
2017-06-12 21:25 ` Randy Dunlap
2017-06-12 22:52 ` Dmitry Torokhov
2018-06-12 20:31 R.F. Burns
2019-06-13 16:16 R.F. Burns
2019-06-13 19:57 ` Theodore Ts'o
2019-06-13 20:07 ` Randy Dunlap
2020-06-18 17:49 R.F. Burns
2020-06-19 3:04 ` Randy Dunlap
2020-06-23 8:03 ` Oleksandr Natalenko
2021-06-15 3:32 R.F. Burns
2021-06-24 14:21 ` Oleksandr Natalenko
2021-06-25 10:12 ` Oleksandr Natalenko
2022-06-12 22:29 R.F. Burns
2023-06-13 3:10 R.F. Burns
2024-06-12 20:16 R.F. Burns
2025-07-01 3:58 R.F. Burns
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=466FC9E2.9060306@grupopie.com \
--to=pmarques@grupopie.com \
--cc=davids@webmaster.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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