Maybe it just AMD's microcode versioning got messed up and this is indeed the latest microcode despite its' lower number, but the only way to check it - is to test both microcodes for their degree of vulnerability to the Spectres. It does not make much sense to release an outdated microcode, assuming its' not an accidental mistake by AMD - so I hope that AMD guy would notice your messages
Ivan
2018-05-27 13:17 GMT+03:00 Mike Banon mikebdp2@gmail.com:
Hi Rudolf,
Please could you try contacting this AMD person again, regarding the problems with this recent microcode update? Because it looks like he noticed your messages since he at least tried to fix, but haven't noticed mine for some reason (regarding the lack of updated 16h microcode; why only 15h and 17h are being updated while 16h is forgotten - I could not understand, and this is relevant since there are some coreboot-supporting 16h boards)
Best regards, Mike Banon
On Sat, May 26, 2018 at 7:13 PM, Rudolf Marek r.marek@assembler.cz wrote:
Hi again,
Dne 23.5.2018 v 21:52 Rudolf Marek napsal(a):
For some reason this firmware update deletes microcode for Trinity CPUs, I tried to contact the person who commit this without any luck. As I have previously written the github page has even newer microcode.
This was fixed, however the old (same) microcode was provided again.
Thanks Rudolf
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot