From: Russ Anderson <rja@efs.americas.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Montecito processor family
Date: Fri, 02 Jun 2006 22:18:58 +0000 [thread overview]
Message-ID: <200606022218.k52MIwjK828087@efs.americas.sgi.com> (raw)
In-Reply-To: <42ADD890.1010406@free.fr>
dann frazier wrote:
>
> On Wed, May 31, 2006 at 07:20:17PM -0600, Matthew Wilcox wrote:
> > We've always felt free to change these strings before. Anyone relying
> > on them for anything more than display-to-the-user purposes is on a
> > losing streak.
>
> Debian Installer uses it for determining the best kernel to install -
> is there a better way? Of course, old installers aren't expected to
> work with new kernels, so the change won't hurt us as long as someone
> notices the change.
That seems like a good reason for family and model to be
numbers straight from the hardware. Applications can key
off the numbers. Then the text "model name" string could
change without breaking applications.
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping : 1
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2006-06-02 22:18 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 [this message]
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
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=200606022218.k52MIwjK828087@efs.americas.sgi.com \
--to=rja@efs.americas.sgi.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