From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Montecito processor family
Date: Tue, 06 Jun 2006 18:04:32 +0000 [thread overview]
Message-ID: <000001c68993$ac26f570$e534030a@amr.corp.intel.com> (raw)
In-Reply-To: <42ADD890.1010406@free.fr>
Luck, Tony wrote on Thursday, June 01, 2006 9:33 AM
> > Why not have "model name" with the text name, like on ia32?
> >
> > vendor_id : GenuineIntel
> > cpu family : 15
> > model : 4
> > model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
> > stepping : 1
>
> This sounds like an excellent plan. We can even use the new
> (in SDM2.2 p. 2:345) PAL_BRAND_INFO call to get the right
> (Intel marketting/legal approved) string. For older systems
> that don't implement PAL_BRAND_INFO we could have some fallback
> code that decodes family/model to Merced/McKinley/Madison.
I would also like to take this opportunity to revamp feature string.
It is way too long, and should be either two or three letter acronym
like x86:
X86 feature string: "flags : fpu vme de pse tsc msr pae mce ... "
- features : branchlong, 16-byte atomic ops
+ features : lb ao
next prev parent reply other threads:[~2006-06-06 18:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 19:03 Montecito processor family Menyhart, Zoltan
2005-06-13 19:17 ` Yu, Fenghua
2005-11-09 13:54 ` Takayoshi Kochi
2005-11-09 15:24 ` Matthew Wilcox
2005-11-10 1:50 ` Takayoshi Kochi
2006-06-01 0:03 ` Luck, Tony
2006-06-01 1:20 ` Matthew Wilcox
2006-06-01 3:06 ` Russ Anderson
2006-06-01 3:30 ` Alex Williamson
2006-06-01 16:32 ` Luck, Tony
2006-06-02 6:51 ` dann frazier
2006-06-02 22:18 ` Russ Anderson
2006-06-03 18:43 ` Luck, Tony
2006-06-03 19:23 ` David Mosberger-Tang
2006-06-05 20:37 ` Luck, Tony
2006-06-06 18:04 ` Chen, Kenneth W [this message]
2006-06-06 18:16 ` Alex Williamson
2006-06-06 18:59 ` Chen, Kenneth W
2006-06-07 9:22 ` Jes Sorensen
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='000001c68993$ac26f570$e534030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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