All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: RE: PC speaker
Date: Tue, 12 Jun 2007 13:08:53 -0700	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKKEHOEIAC.davids@webmaster.com> (raw)
In-Reply-To: <20070612161951.69e54751@the-village.bc.nu>


> > >I'd say impossible. Just disconnect it from the motherboard.
> >
> > The days when hardware *relied* on software (hence, where software
> > could damage hardware) are over.

> Nice theory but you can destroy or render useless a fair amount of PC
> hardware via software, usually because the thing is *DESIGNED* that way
> for convenience. (Flash update interfaces without jumpers, locking
> interfaces for drives etc)

Other great examples are hardware that allows you to control voltages, fan
speeds, and operating frequencies. Sometimes you can overvoltage it directly
and blow it immediately. Other times, you can increase the voltage and
operating frequency and decrease the fan speed to the point where it stops
spinning. This is possible on many modern graphics cards and CPUs.

As far as burning out a speaker goes, if you can drop the frequency to zero
(DC) and get continuous current through the speaker, that could burn it out.
This makes several assumptions, many of which may not be true on modern PCs:

1) It assumes the speaker is a conventional coil speaker, not a piezo
element. (This is certainly true on some PCs, although it's increasingly
false on newer PCs.)

2) It assumes the speaker is DC driven. (I'm pretty sure this was true on
the original IBM PC. Not sure about newer computers.)

3) It assumes you can configure the circuitry that drives the speaker such
that it will stay on. (No idea.)

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.)

On at least some older computers, you could burn out the hardware that drove
the speaker this way. I think it was either the Pet or the Apple ][ (didn't
work on all machines, depended on how much current the speaker drew and
other odd factors). I witnessed an Apple ][e blow out an I/O chip when it
crashed with an output (that was supposed to be pulsed) left in the on
position.

DS



  parent reply	other threads:[~2007-06-12 20:10 UTC|newest]

Thread overview: 53+ 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 [this message]
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
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 --
2023-06-13  3:10 R.F. Burns
2022-06-12 22:29 R.F. Burns
2021-06-15  3:32 R.F. Burns
2021-06-24 14:21 ` Oleksandr Natalenko
2021-06-25 10:12   ` Oleksandr Natalenko
2020-06-18 17:49 R.F. Burns
2020-06-19  3:04 ` Randy Dunlap
2020-06-23  8:03 ` Oleksandr Natalenko
2019-06-13 16:16 R.F. Burns
2019-06-13 19:57 ` Theodore Ts'o
2019-06-13 20:07   ` Randy Dunlap
2018-06-12 20:31 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
2016-08-05 16:51 R.F. Burns
2011-05-28 11:17 Ralf Baechle
2010-06-12 21:32 R.F. Burns
2010-06-12 21:50 ` Daniel Hazelton
2010-06-13  0:07 ` Alan Cox
2009-06-12 21:28 R.F. Burns
2009-06-12 21:40 ` Valdis.Kletnieks
2009-06-13  0:10   ` John Sheu
2008-07-08 17:08 R.F. Burns
2008-07-08 17:38 ` Jan Engelhardt
     [not found] <20080513110322.030a5386.zoup@zoup.org>
     [not found] ` <48296CFF.5000207@keyaccess.nl>
     [not found]   ` <20080513151425.448369e8.zoup@zoup.org>
2008-05-13 11:14     ` [Alsa-user] Pc Speaker Rene Herman
2008-05-22 12:01       ` Arthur Marsh
2000-03-25  1:14 PC Speaker Jon Masters
2000-03-25 17:16 ` Dave Phillips

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=MDEHLPKNGKAHNMBLJOLKKEHOEIAC.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=linux-kernel@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.