From: Pavel Machek <pavel@ucw.cz>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Russell King <rmk@arm.linux.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] /proc/cpuinfo output from some arch
Date: Wed, 10 Jul 2002 02:20:17 +0200 [thread overview]
Message-ID: <20020710002017.GA540@elf.ucw.cz> (raw)
In-Reply-To: <200207070030.g670UbT166497@saturn.cs.uml.edu>
Hi!
> >> /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.
I thought that cpuinfo was ment to be non-chaning after boot?
Perhaps we want /proc/cpu/0/temperature containing single int?
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2002-07-10 19:37 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
2002-07-07 16:25 ` George France
2002-07-10 0:20 ` Pavel Machek [this message]
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=20020710002017.GA540@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox