On 1/16/19 7:53 AM, Mike Banon wrote:
Still recommended to manually update AMD microcodes for Lenovo G505s as
described here?
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
Yes, and it wouldn't be recommended only after my 28273 and 28370
changes will be merged. They haven't been merged yet because AMD
haven't released them to the opensource community.
I think Martin Roth has been communicating with AMD regarding this
matter, but maybe didn't get any reply yet. So we could either wait
few years until the official release or just start using it now. By
the way I'm quite confident that coreboot won't get any DMCA requests
regarding these blobs even if they'll be merged, also because
platomav's famous repositories are fine.
Hi Mike,
Thank you so much for your kind explanation! Without your contribution
and the according pages on dangerousprototypes.com it would be
completely impossible to flash the G505s. Please tell me in case I can
contribute anything (except coding and big money :-)
It seems there are some relevant changes in current Coreboot. Its
configuration menu doesn't have a "Chipset ---> Include CPU microcode in
CBFS" option. And the .config lines mentioned on
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking#AMD_microcode_updates
---------------------------------------------
# CONFIG_CPU_MICROCODE_CBFS_GENERATE is not set
# CONFIG_CPU_MICROCODE_CBFS_EXTERNAL_HEADER is not set
CONFIG_CPU_MICROCODE_CBFS_NONE=y
---------------------------------------------
... can't be found in .config.
The .config file only contains these two lines with the term "MICROCODE"
in it:
# CONFIG_USES_MICROCODE_HEADER_FILES is not set
# CONFIG_HAVE_ROMSTAGE_MICROCODE_CBFS_SPINLOCK is not set
So, I take it, it's all good and prepared for adding the Microcode that
you contributed. Right?
Best regards,
Anac
_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
