Hi Chris, if you'd like to verify the microcodes inside my AMD ucode patch: convert the hexadecimal arrays at their .c files back to binary, extract the microcodes from proprietary UEFI updates for those few AMD boards that are still getting them ( or get them already extracted by platomav from platomav's CPUMicrocodes repository - https://github.com/platomav/CPUMicrocodes ), and compare. They will match 1:1. And if you have any questions about any other parts of my patches, I'll try my best to address them.
On Wed, May 15, 2019 at 12:41 AM Patrick Georgi via coreboot <[email protected]> wrote: > > On Tue, May 14, 2019 at 03:50:18PM -0400, Chris Laprise wrote: > > When I look at review.coreboot.org and the patches have logged commits > > (ostensibly, these are at least hashed) and I see "Patrick Georgi" as > > reviewer... there is no assurance of fidelity from those records? > So what is it you're missing that you require signatures for patches? > > FWIW Gerrit (the software driving review.coreboot.org) supported signed > pushes, but I don't think many people are aware of that or use the feature. > > It's also of somewhat limited use as Gerrit cherry-picks into master which > loses the signature again. > > > Patrick > -- > Google Germany GmbH, ABC-Str. 19, 20354 Hamburg > Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: > Hamburg > Geschäftsführer: Paul Manicle, Halimah DeLaine Prado > _______________________________________________ > coreboot mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
