What's good about the AtomBIOS ROMs: you can use AtomDis tool ( [1] /
[2] ) to get some idea - about what's inside them and what they're
doing. Run "make" to compile it and then use a command like ./atomdis
pci1002,990b.rom F > pci1002,990b.rom.dis . I'm sharing my
disassemblies as .dis files at [3
On 5/20/19 12:02 PM, Mike Banon wrote:
Huge Thanks to Martin Roth, finally we got a permission from AMD to
merge the new microcode patches - and Martin has just merged them !
;-) So the things became slightly easier and luckily now you could
disregard some microcode-related parts of my last messa
Mike Banon:
Huge Thanks to Martin Roth, finally we got a permission from AMD to
merge the new microcode patches - and Martin has just merged them !
;-) So the things became slightly easier and luckily now you could
disregard some microcode-related parts of my last message. And we need
to walk the
Huge Thanks to Martin Roth, finally we got a permission from AMD to
merge the new microcode patches - and Martin has just merged them !
;-) So the things became slightly easier and luckily now you could
disregard some microcode-related parts of my last message. And we need
to walk the same path for
> there is no way for me to compare AMD patches directly since it appears AMD
> doesn't publish them
There is a way: a bit later I will privately share a small list of AMD
boards that are still getting the UEFI updates (to help you to obtain
these microcodes by yourself), and will also share a sm
On 5/16/19 2:35 PM, Mike Banon wrote:
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 the
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 pla
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 mi
On 5/14/19 3:57 PM, awokd via coreboot wrote:
Chris Laprise:
I might put firmware code analysis on my bucket list for the next
life, if I convert to Buddhism. :)
FWIW, those AMD CPU microcode updates are encrypted, so you should also
include cryptanalysis on your bucket list. Don't believe t
Chris Laprise:
I might put firmware code analysis on my bucket list for the next life,
if I convert to Buddhism. :)
FWIW, those AMD CPU microcode updates are encrypted, so you should also
include cryptanalysis on your bucket list. Don't believe the video ones
are, though.
__
On 5/14/19 3:17 PM, Patrick Georgi via coreboot wrote:
On 5/14/19 Chris Laprise wrote:
There are also several (apparently out-of-tree) patches referenced on
the G505s howto:
http://dangerousprototypes.com/docs/Lenovo_G505S_hacking
I'll have to get signatures or similar type of verification for
On 5/14/19 Chris Laprise wrote:
> There are also several (apparently out-of-tree) patches referenced on
> the G505s howto:
>
> http://dangerousprototypes.com/docs/Lenovo_G505S_hacking
>
> I'll have to get signatures or similar type of verification for these as
> well. Any help in this regard would
Hi,
> These appear in only one place, on the coreboot.org Downloads page, and
> are signed with the key:
>
> D861AB74FB933260193399696B249D77269C04E1
>
> The only problem is there is apparently no mention of the signing key
> anywhere else on the coreboot website. I usually look for some explicit,
Hi Chris,
I'll get my public key uploaded to the website shortly. Thanks for
pointing out the issue.
Martin
On Tue, May 14, 2019 at 12:34 PM Chris Laprise wrote:
> Hi all,
>
> I'm about to embark on a coreboot build+flash per Mike Banon's G505s
> page, but before building I want to verify sig
On 5/14/19 2:34 PM, Chris Laprise wrote:
Hi all,
I'm about to embark on a coreboot build+flash per Mike Banon's G505s
page, but before building I want to verify signatures for the source.
These appear in only one place, on the coreboot.org Downloads page, and
are signed with the key:
D861AB
15 matches
Mail list logo