From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Support for GEODE CPUs
Date: Wed, 9 Mar 2005 12:33:44 -0500 [thread overview]
Message-ID: <20050309173344.GD17865@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1110387668.28860.205.camel@localhost.localdomain>
On Wed, Mar 09, 2005 at 05:01:09PM +0000, Alan Cox wrote:
[snip]
> And I have each time pointed out it is wrong over time because
>
> a) "Geode" (Geode GX) runs -m486 code faster than -m586
> b) "Geode" as a name also includes AMD Athlon "Geode NX" processors
> c) Geode GX does not need OOSTORE because the processor manages DMA
> snooping in hardware.
It even looks to me like the Geode GX1 (SCx200 family) is a Cyrix MediaGX
design, the Geode GX2 (Geode GX 533@1.1W and company) I suspect is an
AMD k6 based design (given the 400Mhz speed, and the inclusion of 3Dnow
and MMX), and of course the Geode NX is athlon based.
Now if the Geode GX1 in fact runs faster optimized for 486 rather than
586 (I have been running one as 586tsc since it had mmx and tsc in its
feature list), then I think I will be recompiling my kernel to see if I
can't make this 266MHz GX1 run almost as fast as a 400MHz PXA255 (arm).
Right now it has somewhat lower ethernet bandwidth than the arm.
Len Sorensen
next prev parent reply other threads:[~2005-03-09 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081935.j28JZ433020124@hera.kernel.org>
2005-03-09 17:01 ` Alan Cox
2005-03-09 17:33 ` Lennart Sorensen [this message]
2005-03-09 21:59 ` Alan Cox
2005-03-09 22:23 ` Lennart Sorensen
2005-03-09 23:26 ` David Vrabel
2005-03-10 0:06 ` Alan Cox
2005-03-11 1:42 ` Andrew Morton
2005-03-11 11:02 ` Alan Cox
2005-03-11 14:13 ` Lennart Sorensen
2005-03-21 23:41 ` Andrew Morton
2005-03-22 1:09 ` Kianusch Sayah Karadji
2005-03-22 7:13 ` Andrew Morton
2005-03-22 8:01 ` Kianusch Sayah Karadji
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=20050309173344.GD17865@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--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
all inboxes | Powered by JetHome®