[syslinux] Distilling down a small set of useful system data

Kevin Landreth crackerjackmack at gmail.com
Wed Apr 27 17:45:17 PDT 2011


On Wed, Apr 27, 2011 at 6:20 PM, H. Peter Anvin <hpa at zytor.com> wrote:

> On 04/27/2011 03:51 PM, Kevin Landreth wrote:
> >
> > As a suggestion,  I believe the primary CPU information is returned
> > from eax in "00000001" [1]. So what if you just returned an comma
> > separated string of hex encoded registers eax,ebx,ecx,edx [2] ?  This
> > would always be within the 80 character limit as requested and usable
> > to some extent. While not consumable with the naked eye, it is
> > parseable and /fairly/ standardised.  One could always re-implement
> > the ifcpu.c32 parsing in whatever desired language on the HTTP server.
> >
> > Just a suggestion, don't know if it helps any.
> >
> > [1] Relevant data from "cpuid":
> >    eax in       eax          ebx          ecx         edx
> > 00000001 00010676 01040800 000ce33d bfebfbff
> >
> > [2] "0x00010676,0x01040800,0x000ce33d,0xbfebfbff"
> >
>
> Sorry, there are a bunch of other bitflags... for example, the long mode
> (x86-64) flag is CPUID level 0x80000001.
>
>        -hpa
>
> Awe shucks.  well, that's what I get for not looking into it further before
suggesting it.

-- 
Kevin Landreth



More information about the Syslinux mailing list