From: Jan Engelhardt <jengelh@computergmbh.de>
To: "R.F. Burns" <burnsrf@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PC speaker
Date: Tue, 12 Jun 2007 17:09:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706121709160.19578@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <Pine.LNX.4.64.0706121556510.19578@fbirervta.pbzchgretzou.qr>
On Jun 12 2007 15:57, Jan Engelhardt wrote:
>On Jun 12 2007 09:54, R.F. Burns wrote:
>> On 6/12/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
>>> On Jun 12 2007 08:45, R.F. Burns wrote:
>
>>> > Is it possible to write a kernel module which, when loaded, will blow the
>>> > PC
>>> > speaker?
>>>
>>> Define blow.
>>> (As in "damage"?)
>>
>> Yes. As in, blow it out/damage it so that it is no longer usable.
>
>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.
Jan
--
next prev parent reply other threads:[~2007-06-12 15:09 UTC|newest]
Thread overview: 49+ 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 [this message]
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
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
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
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=Pine.LNX.4.64.0706121709160.19578@fbirervta.pbzchgretzou.qr \
--to=jengelh@computergmbh.de \
--cc=burnsrf@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).