search for: dmi_processor

...trying to re-image the 8,000 odd boxes spread round the globe. This was hugely based on Erwan Velu's dmitest.c circa 3.20. I decided I'd better update my com32 module and compile it against 3.7x but I found that the "lm" flag which I relied on to determine 32/64 bit was gone from dmi_processor.h. I then thought the solution was obviously to use the cpuid.h code which had the "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...

Hi Erwan, First off, many thanks for your wonderful addition to syslinux: dmitest.c32 and another thankyou to hpa for it's inclusion. I need to ask if you are missing a couple of definitions in dmi_processor.h, specifically, the "long mode" flag. I need to use this flag to determine whether a machine is 64-bit capable or not. There is a great web page explaining the "long mode" flag at: http://www.mega-tokyo.com/osfaq/Tell%20me%20about%20x86%2064%20bits%20CPU%20... >From the w...

...dition 'code<=13' is redundant. is caused by missing subtraction of 1 in strlcpy(dmi->base_board.type, type[code], It should be strlcpy(dmi->base_board.type, type[code - 1], ----------------------------------------------------------------- [com32/gpllib/dmi/dmi_processor.c:381] -> [com32/gpllib/dmi/dmi_processor.c:380]: (warning) Array 'upgrade[23]' accessed at index 24, which is out of bounds. Otherwise condition 'code<=25' is redundant. is caused by missing commas in lines "Socket 939" /* 0x12 */ "...

> On Jul 10, 2015 5:29 PM, "poma via Syslinux" <syslinux at zytor.com> wrote: > > > The same as with the ISOLINUX, stable and git. > > Only this time has nothing to do with the menu. > > 1) EXTLINUX is no longer a discrete variant. The installer extlinux now > installs SYSLINUX. > 2) William Kensington already saw a similar behavior wherein an