[coreboot] Dont filter supported CPUs on a mainboard by the CPUID

i1w5d7gf38keg at tutanota.com i1w5d7gf38keg at tutanota.com
Thu Feb 23 00:31:38 CET 2017


What is the benefit of such a list? I cant see any benefit. Its only additional work that is useless.

A example for CPUID-List blocking functionality is commit I63d308477a22a9e55ceed1b6b36e63a3044c2354


22. Feb 2017 23:15 by tpearson at raptorengineering.com:


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 02/22/2017 05:07 PM, > i1w5d7gf38keg at 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Mozilla - > http://enigmail.mozdev.org
>
> iQEcBAEBAgAGBQJYrht0AAoJEK+E3vEXDOFb/S0H/17w88+kNxBcPm+V+hPkpMDE
> r6FcyfSO4tm96b/lPgkhK78jxqighQHD7sR2keFWAO+5hwRQfuZwHYVsPa1WmrUN
> u3J08Mgl5r/xTyoBEp/CRxAGD5FaN+NOYQgBVFh8J6IGLBeYJxcmv/PdQmctvi+J
> lXuqepsei5TLDIn+9hE3U2Dbh0H/6m8+YFFRbeYbcoNfyuRFE5APks3s+QOjqa4w
> wBR30fafSBkj4DyGMSzD5yZbOLl/SJDhT1FjvWlx5H4YwKv/vltAPYhq1enaJkRf
> 61cpl2Prfin4DvpWGU/geTi94bskBo8D8sE1SHumoGXIQ+maICPh/ndtIRNUJIQ=
> =UsCc
> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20170223/f5980be8/attachment.html>


More information about the coreboot mailing list