From: Shaya Potter <spotter@cs.columbia.edu>
To: Dave Jones <davej@suse.de>
Cc: Steve Brueggeman <brewgyman@mediaone.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Athlon PSE/AGP Bug
Date: 22 Jan 2002 10:27:35 -0500 [thread overview]
Message-ID: <1011713259.904.6.camel@zaphod> (raw)
In-Reply-To: <20020122135843.B16444@suse.de>
In-Reply-To: <1011610422.13864.24.camel@zeus> <20020121.053724.124970557.davem@redhat.com>, <20020121.053724.124970557.davem@redhat.com>; <20020121175410.G8292@athlon.random> <3C4C5B26.3A8512EF@zip.com.au> <o7cp4ukpr9ehftpos1hg807a9hfor7s55e@4ax.com> <1011678359.904.4.camel@zaphod> <20020122135843.B16444@suse.de>
you're right, it's a typo on my part. I hit 2 twice instead of 6.
woops
On Tue, 2002-01-22 at 07:58, Dave Jones wrote:
> On Tue, Jan 22, 2002 at 12:45:59AM -0500, Shaya Potter wrote:
> > athlon XP 1800 is a cpuid 622 (aka an A5)
> > at least my 2 XP 1800+s are 622, so I assume all are (could be wrong)
>
> Unless you have /proc/cpuinfo output that says otherwise, this is
> wrong. 622 is the olde Athlon (0.18um) Rev A2.
>
> XP is 662 with cachesize >=256 with bit 19 of capflags==0
>
> (Determining new Duron/Athlon XP/Athlon MP is quite messy,
> see x86info source for gory details)
>
> --
> | Dave Jones. http://www.codemonkey.org.uk
> | SuSE Labs
--
spotter@{cs.columbia.edu,yucs.org}
http://yucs.org/~spotter/
next prev parent reply other threads:[~2002-01-22 15:30 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 10:53 Athlon PSE/AGP Bug Reid Hekman
2002-01-21 13:37 ` David S. Miller
2002-01-21 13:50 ` Arjan van de Ven
2002-01-21 16:58 ` jepler
2002-01-21 17:26 ` Ed Sweetman
2002-01-21 22:14 ` David S. Miller
2002-01-21 16:54 ` Andrea Arcangeli
2002-01-21 17:57 ` Reid Hekman
2002-01-21 18:17 ` Andrew Morton
2002-01-21 19:11 ` Harold Campbell
2002-01-21 22:23 ` David S. Miller
2002-01-22 0:39 ` Andrea Arcangeli
2002-01-22 1:08 ` David S. Miller
2002-01-22 7:05 ` Ville Herva
2002-01-22 7:08 ` David S. Miller
2002-01-22 8:05 ` Daniel Robbins
2002-01-22 0:26 ` Stuart Young
2002-01-22 0:36 ` Steve Brueggeman
2002-01-22 1:02 ` Steve Brueggeman
2002-01-22 20:13 ` Florian Weimer
2002-01-22 22:14 ` Ed Sweetman
2002-01-22 22:52 ` Steve Brueggeman
2002-01-22 23:49 ` Rik van Riel
2002-01-23 0:36 ` Stuart Young
2002-01-23 1:20 ` Rene Rebe
2002-01-23 2:01 ` Gustavo Zacarias
2002-01-23 2:11 ` Tom Hornyak
2002-01-22 22:32 ` Steve Brueggeman
2002-01-22 5:45 ` Shaya Potter
2002-01-22 12:58 ` Dave Jones
2002-01-22 15:27 ` Shaya Potter [this message]
2002-01-22 18:52 ` Greg
2002-01-22 22:08 ` Rene Rebe
2002-01-21 22:19 ` David S. Miller
2002-01-22 0:37 ` Andrea Arcangeli
2002-01-22 0:43 ` Russell King
2002-01-22 0:53 ` Andrea Arcangeli
2002-01-22 0:55 ` Russell King
2002-01-22 1:07 ` David S. Miller
2002-01-22 1:27 ` Andrea Arcangeli
2002-01-22 16:57 ` David Woodhouse
2002-01-21 19:37 ` Alan Cox
2002-01-21 19:34 ` David Weinehall
2002-01-21 19:53 ` Sipos Ferenc
2002-01-22 6:32 ` Paul G. Allen
-- strict thread matches above, loose matches on Subject: below --
2002-01-22 14:12 Halpaap, Mark (CETA)
2002-01-22 14:51 ` Ed Sweetman
2002-01-22 23:21 ` Ian Molton
2002-01-22 14:51 ` João Seabra
2002-01-23 18:49 ` Marek Mentel
2002-01-22 17:59 Ben Carrell
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=1011713259.904.6.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=brewgyman@mediaone.net \
--cc=davej@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox