From: Andi Kleen <ak@muc.de>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, mark.langsdorf@amd.com
Subject: Re: Celistica with AMD chip-set
Date: 30 Aug 2004 19:45:22 +0200
Date: Mon, 30 Aug 2004 19:45:22 +0200 [thread overview]
Message-ID: <20040830174522.GA59551@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0408301318290.22149@chaos>
> It is NOT "blindly" overwritten. We know what was in that register
> (0x2c01).
You don't, it depends on the BIOS version and the hardware revision.
-Andi
next prev parent reply other threads:[~2004-08-30 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2yV1c-29L-7@gated-at.bofh.it>
[not found] ` <2yVb1-2ft-57@gated-at.bofh.it>
2004-08-30 15:28 ` Celistica with AMD chip-set Andi Kleen
2004-08-30 17:20 ` Richard B. Johnson
2004-08-30 17:45 ` Andi Kleen [this message]
2004-08-30 14:02 Richard B. Johnson
2004-08-30 13:15 ` Alan Cox
2004-08-30 15:04 ` Arthur Perry
2004-08-30 15:34 ` Arthur Perry
2004-08-30 17:26 ` Richard B. Johnson
2004-08-30 17:17 ` Richard B. Johnson
2004-08-30 18:13 ` Arthur Perry
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=20040830174522.GA59551@muc.de \
--to=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=root@chaos.analogic.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