From: Peter Samuelson <peter@cadcamlab.org>
To: ryan <ryan@javien.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Change of /proc/cpuinfo format
Date: Tue, 5 Dec 2000 17:21:22 -0600 [thread overview]
Message-ID: <20001205172122.H6567@cadcamlab.org> (raw)
In-Reply-To: <3A2D7505.2BB48C48@javien.com>
In-Reply-To: <3A2D7505.2BB48C48@javien.com>; from ryan@javien.com on Tue, Dec 05, 2000 at 03:06:45PM -0800
> I'm not quite sure why the name change is necessary, and even if one
> wants to keep the name change there is a discontunity of cpuinfo
> formats and programs which intend to run on kernels 2.2 and 2.4 needs
> to know this...
The reason is that HPA, who did the recent IA32 CPU detection cleanup,
felt that the information reported in the new 'features' field was
sufficiently different from that reported in the old 'flags' field that
it was worth renaming -- so that programs wouldn't try to rely on the
old flag names.
(Specifically: some flags were renamed to be distinct between Intel,
AMD, etc, because the exact behavior of the flag may vary between
brands.)
> - "features\t:",
> + "flags\t:",
This patch is already in test12pre5, and is wrong. You need two tabs
after 'flags'.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-05 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 23:06 Change of /proc/cpuinfo format ryan
2000-12-05 23:21 ` Peter Samuelson [this message]
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=20001205172122.H6567@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@javien.com \
/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.