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

Timothy Pearson tpearson at raptorengineering.com
Thu Feb 23 00:52:04 CET 2017


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/22/2017 05:49 PM, i1w5d7gf38keg at tutanota.com wrote:
>  Thanks for the information. Then maybe just dont stop booting when
> CPUID is missing. Just add a line to the coreboot log. Something like:
> "WARNING: Unknown CPU ID detected. Please report to the coreboot mailing
> lists if the machine is working fine"
> 
> Then you still have the same functionality as you told. CPUs that
> require different handling on different revisions can still be
> maintained different.
> 
> People are also way more motivated to report some unstable working CPUs
> then when they flash coreboot and the system simply didnt work at all
> and without reading the logfiles it looks like its completely dead (no
> screen, nothing, just fans are on).

And with that, I'll turn this over for the other members on the list to
comment on this suggestion.  I don't care strongly one way or another,
provided the warning is at ALERT status so it shows up even with logging
mostly disabled.

- -- 
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/

iQEcBAEBAgAGBQJYriQiAAoJEK+E3vEXDOFbKWcIAIQgDNEdbmh3nTy5rleMlakF
0kph3iwnvAXWynNq8hPu+4iHqbHWpPgUF9GFJly0O3P2gQ23Buo0slLPd6Eq7Xra
fDxHZQWegWM07NPOLi94wtDe0KRMMPmr2M8b4ZVyyIPeRTPW4Dw2UpK4sAbUWaiu
H30Jzb4EaUOjMYo1j9bqn9Mf0mclgbnsLCkDLUnN9f/Va98a+m9KvQ55AwIkn3SX
PReHQ273RRQMIYgCm0qwyySeUovxGWO4bKkViuGE4NkqkA+yXKpPsdMMsw7oTMpY
N4MfISLexn2ZeBR2kxW5gPqoL4gr3ofnivVqLfaKmd2SWMeeua+mXB4EFKurUyk=
=B4xv
-----END PGP SIGNATURE-----



More information about the coreboot mailing list