Displaying 2 results from an estimated 2 matches for "s_cpu_flags".
Did you mean:
cpu_flags
2008 Oct 15
1
Syslinux Digest, Vol 67, Issue 10
...quot;lm" flag... however I find that I cannot include both:
#include "dmi/dmi.h"
#include <cpuid.h>
As they have conflicting ideas of what the cpu flags structure should be:
In file included from dugtest.c:30:
../../com32/include/cpuid.h:80: error: conflicting types for 's_cpu_flags'
../../com32/include/dmi/dmi_processor.h:103: error: previous
declaration of 's_cpu_flags' was here
While I can maybe code around this by changing the header files, I
thought I should point this out and ask that, maybe, dmi.h be made
more modular and rely on cpuid.h for CPU information...
2006 Aug 28
2
Extending dmitest to check for Long Mode (aka 64 versus 32 bit)
...:
NULL, /* 30 */
In the Linux kernel I see that /proc/cpuinfo is determined through the
/usr/include/asm/cpufeature.h include as:
#define X86_FEATURE_LM (1*32+29) /* Long Mode (x86-64) */
Would I simply need to Change the NULL entry to a string in
cpu_flags_strings table, add a bool in s_cpu_flags and then
dmi.c would automagically set the boolean correctly ?
I could then modify dmitest to check for Long Mode and achieve
my goal.
Any help hugely appreciated!
Cheers,
Doug
--
The big print giveth and the small print taketh away.