From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Pavel Machek <pavel@suse.cz>
Cc: textshell@neutronstar.dyndns.org,
Dominik Brodowski <linux@brodo.de>,
davej@suse.de, Linux kernel <linux-kernel@vger.kernel.org>,
Henrik Persson <nix@syndicalist.net>
Subject: Re: 2.6.0-test1: CPUFreq not working, can't find sysfs interface
Date: Wed, 23 Jul 2003 07:28:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307230720190.8208@chaos> (raw)
In-Reply-To: <20030723111320.GB729@zaurus.ucw.cz>
On Wed, 23 Jul 2003, Pavel Machek wrote:
[SNIPPED...]
> Pavel
> Hardware that lets software kill it deserved that.
Don't touch the Motorola 56xxx DSP, then. There are several
"insane instructions" that will smoke the device (programming
a pin for both input and output at the same time). There are
many other chips, often used on Motherboards, that have
programmable pins (even the AMD SC520)... These can be destroyed
by software.
Also, the bits for setting the power supply voltages to be
applied to your CPU are available in I/O space on many motherboards.
Try your 2.5 volt CPU on 5.0 volts. It will melt the solder that
holds the socket to the board!
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-07-23 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-20 15:02 2.6.0-test1: CPUFreq not working, can't find sysfs interface textshell
2003-07-20 17:45 ` Henrik Persson
2003-07-20 21:12 ` textshell
2003-07-22 12:08 ` Dominik Brodowski
2003-07-22 14:18 ` textshell
2003-07-22 14:23 ` Dominik Brodowski
2003-07-22 14:42 ` Dave Jones
2003-07-22 14:53 ` textshell
2003-07-23 11:13 ` Pavel Machek
2003-07-23 11:28 ` Richard B. Johnson [this message]
2003-07-23 12:30 ` Pavel Machek
2003-07-23 16:36 ` Dominik Brodowski
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.53.0307230720190.8208@chaos \
--to=root@chaos.analogic.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=nix@syndicalist.net \
--cc=pavel@suse.cz \
--cc=textshell@neutronstar.dyndns.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).