[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 18 May 2007 17:50:09 +0200
Here's a patch to implement cpuid.mod. This module checks for CPU features
(currently only the long_mode flag, but more could be added if needed) using
cpuid. The idea behind this is that grub.cfg scripts can use it to decide
wether a 64-bit or 32-bit Linux image should be boot (e.g. like Debian
multiarch CDs do). I haven't investigated what the syntax for that hack
would be, although I assume it's possible.
Cpuid detection code has been borrowed from gcc and is FSF-copyrighted.
I'm not sure where would the file go. I noticed that other utility modules
(e.g. hello/hello.c) add themselves in the top dir, so I suppose i386/cpuid.c
would be ok?
Or perhaps we could have an "util" dir for modules?
My spam trap is address@hidden Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
Description: Text Data
- CPUID module,
Robert Millan <=