All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: rmk@arm.linux.org.uk (Russell King)
Cc: hpa@zytor.com (H. Peter Anvin), linux-kernel@vger.kernel.org
Subject: Re: [OT] /proc/cpuinfo output from some arch
Date: Sat, 6 Jul 2002 20:30:37 -0400 (EDT)	[thread overview]
Message-ID: <200207070030.g670UbT166497@saturn.cs.uml.edu> (raw)
In-Reply-To: <20020707002006.B5242@flint.arm.linux.org.uk> from "Russell King" at Jul 07, 2002 12:20:06 AM

Russell King writes:
> On Sat, Jul 06, 2002 at 03:16:07PM -0700, H. Peter Anvin wrote:

>> /proc/cpuinfo was *definitely* meant to be parsed by programs.
>> Unfortunately, lots of architectures seems to have completely missed
>> that fact.
>
> Sigh, its a shame such things aren't documented somewhere in the
> kernel tarball.

Ah, but you're supposed to remember the history!
The colons were added to make parsing easier.
I think that was done after somebody added spaces
on the left, and lots of app developers screamed
that the format had become hopeless.

Right now I'm looking to get the temperature,
clock speed, and voltage. I get the first two
on PowerPC hardware, but it's not obvious what
mess an SMP system would spit out.



  parent reply	other threads:[~2002-07-07  0:28 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
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 [this message]
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
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=200207070030.g670UbT166497@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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.