From: Russell King <rmk@arm.linux.org.uk>
To: Andreas Schwab <schwab@suse.de>
Cc: "Witek Krêcicki" <adasi@kernel.pl>, linux-kernel@vger.kernel.org
Subject: Re: [OT] /proc/cpuinfo output from some arch
Date: Sat, 6 Jul 2002 22:12:05 +0100 [thread overview]
Message-ID: <20020706221205.A5242@flint.arm.linux.org.uk> (raw)
In-Reply-To: <jen0t4g35k.fsf@sykes.suse.de>; from schwab@suse.de on Sat, Jul 06, 2002 at 07:46:47PM +0200
On Sat, Jul 06, 2002 at 07:46:47PM +0200, Andreas Schwab wrote:
> Processor : Intel StrongARM-110 rev 4 (v4l)
Note that this could also be something like:
Processor : ARM/VLSI Arm1020id(wb)BRR rev 1 (v4)
or:
Processor : ARM ARM926EJ-Sid(wb)RR rev 2 (v5)
It might change further if the manufacturer decides to have a space
in their name. Basically, /proc/cpuinfo was never meant to be passed
by programs, and its not something I'd like to support with the current
format.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-07-06 21:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 9:16 [OT] /proc/cpuinfo output from some arch Witek Kręcicki
2002-07-06 11:12 ` Richard Zidlicky
2002-07-06 12:50 ` Dr. David Alan Gilbert
2002-07-06 17:46 ` Andreas Schwab
2002-07-06 21:12 ` Russell King [this message]
2002-07-06 21:25 ` Thunder from the hill
2002-07-06 22:16 ` H. Peter Anvin
2002-07-06 23:20 ` Russell King
2002-07-06 23:27 ` H. Peter Anvin
2002-07-07 0:30 ` Albert D. Cahalan
2002-07-07 16:25 ` George France
2002-07-10 0:20 ` Pavel Machek
2002-07-10 22:14 ` H. Peter Anvin
2002-07-10 23:15 ` Russell King
2002-07-10 23:47 ` Alan Cox
2002-07-10 23:37 ` Russell King
2002-07-10 23:45 ` Thunder from the hill
2002-07-11 2:22 ` Alan Cox
2002-07-11 0:52 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-07-06 12:15 Holzrichter, Bruce
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=20020706221205.A5242@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=adasi@kernel.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=schwab@suse.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.