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? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:18 EST