From: Michael Riepe <michael.riepe@googlemail.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
tglx@linutronix.de
Subject: Re: Identifying Intel Atom Z500PT
Date: Wed, 08 Apr 2009 19:46:11 +0200 [thread overview]
Message-ID: <49DCE2E3.7050700@googlemail.com> (raw)
In-Reply-To: <20090407222144.GU5367@pengutronix.de>
Hi!
Robert Schwebel wrote:
> Does anyone have an idea how to properly identify an Atom Z500PT cpu?
> The get_model_name() mechanics in arch/x86/kernel/cpu/common.c uses
> cpuid() to find out about the brand id, which is "Genuine Intel(R) CPU"
> with family 6 and model 28.
Family 6, model 28, stepping 2 seems to be common to all current Atoms
-- my 330 reports the same. There are some flags, however, that
currently only appear in the Z series, e.g. vmx is not available on the
230/330/N270. To differentiate between the latter, you could look for
64-bit support (which is missing in the N270) and the number of cores.
Besides that, the 230/330 models lack the speedstep feature.
I don't know if there's a way to distinguish a -P model from a -PT
model. But from a software point of view, they should be identical anyway.
> Below is the output of /proc/cpuinfo on that box:
>
> root@phyCORE:~ cat /proc/cpuinfo | grep model | head -n 2
> model : 28
> model name : Genuine Intel(R) CPU @ 1.10GHz
Strange - the 330 reports:
model name : Intel(R) Atom(TM) CPU 330 @ 1.60GHz
(running 2.6.29).
--
Michael "Tired" Riepe <michael.riepe@googlemail.com>
X-Tired: Each morning I get up I die a little
next prev parent reply other threads:[~2009-04-08 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 22:21 Identifying Intel Atom Z500PT Robert Schwebel
2009-04-08 0:56 ` Thomas Gleixner
2009-04-08 6:56 ` Robert Schwebel
2009-04-08 17:46 ` Michael Riepe [this message]
2009-04-08 18:24 ` Robert Schwebel
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=49DCE2E3.7050700@googlemail.com \
--to=michael.riepe@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=r.schwebel@pengutronix.de \
--cc=tglx@linutronix.de \
/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.