This should not be an excuse to be sloppy.
> We could have a standard part /proc/cpuinfo part for those
> applications that care about this and a architecture-specific part.
User continues to scratch head and can't figure out why different
architectures display the same type of information in completely different
formats...
> The standard part should have:
>
> global: the port name, architecture type, number of cpus on the
> system, number of active cpus on the system.
>
> per cpu: the cpu type, the fpu type, mmu type, bogomips.
>
> The rest should be architecture dependant.
And why pray tell does one huge /proc/cpuinfo entry make more sense than
e.g /proc/cpu/0 /proc/cpu/1 /proc/cpu/2?
The SCSI system does it this way for multiple adaptors, IMHO it's The
Right Way. Stuffing all the multiple CPU info in a single entry is the
M$-way.
-Dan