Re: /proc/cpuinfo format - arch dependent!

I don't want to butt in on a private fight but, philosophically,
I would argue that it is up to the kernel to report the real
hardware configuration in an easy to use, and extensible, way.

This only needs to be done once. To argue about what application
writers could or should use, based on what happens today is
just a cop-out; the only thing one must say is that if the app
dosn't understand the architecture it must provide defaults.

- Brian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: /proc/cpuinfo format - arch dependent!
    • From: Jim Nance <[email protected]>
  • Re: /proc/cpuinfo format - arch dependent!
    • From: Bill Davidsen <[email protected]>
  • Re: /proc/cpuinfo format - arch dependent!
    • From: Chris Friesen <[email protected]>
  • Re: /proc/cpuinfo format - arch dependent!
    • From: [email protected] (Lennart Sorensen)

• Prev by Date: Re: [ANNOUNCE] hotplug-ng 002 release
• Next by Date: Re: [PATCH] Priority Lists for the RT mutex
• Previous by thread: Re: /proc/cpuinfo format - arch dependent!
• Next by thread: Re: /proc/cpuinfo format - arch dependent!
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]