From: Andreas Bombe <bombe@informatik.tu-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Dual athlon XP 1800 problems
Date: Fri, 4 Jan 2002 03:15:53 +0100 [thread overview]
Message-ID: <20020104021553.GB3474@storm.local> (raw)
In-Reply-To: <3C311B00.FFB58648@get2chip.com> <20020101032335.A11129@suse.de> <1009868304.27412.2.camel@zaphod> <20020103165321.GA737@bombe.modem.informatik.tu-muenchen.de> <a125gv$l3b$1@cesium.transmeta.com>
In-Reply-To: <a125gv$l3b$1@cesium.transmeta.com>
On Thu, Jan 03, 2002 at 09:48:15AM -0800, H. Peter Anvin wrote:
> Followup to: <20020103165321.GA737@bombe.modem.informatik.tu-muenchen.de>
> By author: Andreas Bombe <bombe@informatik.tu-muenchen.de>
> In newsgroup: linux.dev.kernel
> >
> > The identification string is written by the BIOS. Yours didn't know
> > about XPs so it misidentified them as MPs. Upgrade your BIOS if this
> > bugs you.
> >
> > If ID string contradicts what you think you bought, don't trust the ID
> > string.
> >
>
> This seems very odd. I thought in Athlon processors the ID string
> came from the *CPU* (via CPUID), not the BIOS...
It comes from there, but it is written there by the BIOS for Athlon (and
I guess Duron, too).
http://www.heise.de/newsticker/data/jow-18.10.01-000/ (in German)
I searched a bit with Google but couldn't find an English page with that
info right now.
--
Andreas Bombe <bombe@informatik.tu-muenchen.de> DSA key 0x04880A44
next prev parent reply other threads:[~2002-01-04 2:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 2:12 Dual athlon XP 1800 problems ccroswhite
2002-01-01 3:23 ` Dave Jones
2002-01-01 3:40 ` Jeffrey H. Ingber
2002-01-01 4:46 ` Adam Schrotenboer
2002-01-01 6:58 ` Shaya Potter
2002-01-03 16:53 ` Andreas Bombe
2002-01-03 17:07 ` Dave Jones
2002-01-03 19:07 ` Shaya Potter
2002-01-03 17:48 ` H. Peter Anvin
2002-01-03 18:02 ` Dave Jones
2002-01-04 0:36 ` H. Peter Anvin
2002-01-04 2:15 ` Andreas Bombe [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-01 15:21 Dr. David Alan Gilbert
2002-01-03 17:08 ` Andreas Bombe
2002-11-15 10:31 David Crooke
2002-11-15 11:55 ` Alastair MacGregor
2002-11-15 14:54 ` Alan Cox
2002-11-15 14:40 ` Dave Jones
2002-11-15 17:19 ` Willy Tarreau
2002-11-15 18:38 ` erich
2002-11-15 17:26 ` Ken Witherow
2002-11-15 17:40 ` steve roemen
2002-11-15 18:21 ` Ken Witherow
2002-11-15 18:51 ` Alastair MacGregor
2002-11-16 3:04 ` Alan Cox
2002-11-16 15:11 Kevin Brosius
2002-11-16 15:14 ` Kevin Brosius
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=20020104021553.GB3474@storm.local \
--to=bombe@informatik.tu-muenchen.de \
--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.