> So personally, I don't care what goes into /proc/cpuinfo, I don't care
> if I get Bogomips ratings instead of MHz, I don't care if I get an
> entire list of Intel-only bugs, and I don't even care if I get wrong CPU
> stepping information on non-Intel CPUs.
Please distinguish between _wrong_ stepping information and stepping
information reported being written in format different than by the CPU
manufacturer if the manufacturer decides to confuse users by having
two different stepping types (one reported by the CPU and one in the
documentation).
> Also, I post my fixes to the kernel list, because I believe other people
> have the same problems, and so perhaps by sharing information, we can
> help each other.
>
> However, I always feel a resistance to change. An example: 7 or 8 months
> ago, I posted both my observation of a kernel oops and a patch that
> worked around it. Until now, it had not made it to the kernel. And only
> because I insisted until I got half-flamed by Linus, people took notice.
Well, as I still partially maintain the x86 detection code, just send
(or Cc) all patches to me.
> When the average Linux user sees a Bogomips line in /proc/cpuinfo, he
> doesn't understand what this thing means. If it said MHz, OK.
He doesn't understand and he doesn't need to understand. If he wants
CPU clock speed, he can simply get a speed measuring utility.
> Same goes for all the bug related lines, some of which are so old that
> they only apply to 386 CPUs (and people who are still using 386s don't
> parse /proc/cpuinfo, believe me).
I think they do as I know some counterexamples.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "If you are feeling good, don't worry. You'll get over it."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu