From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Brown, Len" <len.brown@intel.com>
Cc: Tony Lindgren <tony@atomide.com>,
Erik Slagter <erik@slagter.name>, Andrew Morton <akpm@osdl.org>,
Joerg Sommrey <jo@sommrey.de>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
arjan@infradead.org
Subject: RE: [PATCH] amd76x_pm: C3 powersaving for AMD K7
Date: Thu, 02 Feb 2006 01:50:41 +0000 [thread overview]
Message-ID: <1138845041.5557.20.camel@localhost.localdomain> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005EC94C3@hdsmsx401.amr.corp.intel.com>
On Mer, 2006-02-01 at 20:35 -0500, Brown, Len wrote:
> This endeavor is full of risk, and I would be extremely careful
> about enabling features that the BIOS explicitly disabled --
> unless the hardware manufacturer publicly publishes
> support for the feature, or the errata that you're working around.
Folks had code that supported AMD76x by banging the hardware directly.
On some AMD76x systems it caused corruption. Nobody AFAIK ever figured
out if it was an errata (nothing obvious in the docs/errata list) or a
bug in the code doing the banging on the chip or some other bit of
hardware on the mainboard that needed extra handling.
Alan
next prev parent reply other threads:[~2006-02-02 1:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 1:35 [PATCH] amd76x_pm: C3 powersaving for AMD K7 Brown, Len
2006-02-02 1:50 ` Alan Cox [this message]
2006-02-02 9:50 ` Erik Slagter
2006-02-02 19:38 ` Tony Lindgren
2006-02-03 9:21 ` Erik Slagter
2006-02-03 9:33 ` Pavel Troller
2006-02-03 9:39 ` Erik Slagter
2006-02-03 10:14 ` Pavel Troller
2006-02-03 10:28 ` Erik Slagter
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 18:40 Brown, Len
2006-02-04 10:31 ` Erik Slagter
2006-02-04 10:49 ` Pavel Troller
2006-02-03 18:28 Brown, Len
2006-02-03 18:20 Brown, Len
2006-02-03 8:45 Brown, Len
2006-02-03 9:35 ` Erik Slagter
2006-02-03 10:31 ` Pavel Troller
2006-02-03 14:16 ` Joerg Sommrey
2006-02-03 15:59 ` Juhani Rautiainen
2006-02-03 17:02 ` Erik Slagter
2006-02-08 20:10 ` Pavel Machek
2006-02-02 22:24 Joerg Sommrey
2006-02-02 22:37 ` Andrew Morton
2006-02-03 7:03 ` Joerg Sommrey
2006-02-02 22:43 ` Dave Jones
2006-02-01 18:11 Brown, Len
2006-02-01 18:18 ` Erik Slagter
2006-02-01 18:40 ` Tony Lindgren
2006-02-01 19:13 ` Joerg Sommrey
2006-01-31 18:55 Joerg Sommrey
2006-02-01 3:34 ` Andrew Morton
2006-02-01 10:25 ` Erik Slagter
2006-02-01 17:20 ` Tony Lindgren
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=1138845041.5557.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=erik@slagter.name \
--cc=jo@sommrey.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
/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