-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/22/2017 05:07 PM, i1w5d7gf38keg@tutanota.com wrote:
There is a Filter to stop booting when the CPUID is not in a list of supported CPUs. This filter does not make sense in the real world usage. For example socket 775: When you enter a working cpu, then it boots. In some cases the coreboot code didnt work with a CPU where it should. For example some Pentium-4 CPUs. Then it crashes even before raminit. But when you add a CPU that "would" work but is not listed in the CPUID lists from coreboot, the machine didnt boot. If you simply add the CPUID to the list everything works fine.
In short: The only thing this CPUID list is doing is blocking functionality and adding work (a list that have to be maintained). Nothing else. If a CPU is not supported, it crashes after 4-5 lines of logfile - even before the raminit. Thats before this CPUID list is been checked.
Please remove those CPUID lists.
I would recommend the lists be retained. Presumably the individual(s) that wrote the CPU / northbridge support code are aware of the CPUs that the code is designed to work with, and using CPUs that were never intended with that code does entail a certain amount of risk. Individuals capable of mitigating this risk / verifying processor functionality are also capable of modifying the CPUID list.
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com