On Sun, Jan 10, 2016 at 4:40 AM, Paul Menzel
Dear coreboot folks,
on the ASRock E350M1, I lately noticed that the SeaBIOS banner takes
longer to appear. And looking at the logs board status , the time
stamps stored in CBMEM confirm this.
What were your typical times like?
$ grep 1st asrock/e350m1/4.2-*/*/coreboot_timestamps.txt
Unfortunately, there was a time, where I had forgotten to select this
option, so I am still bisecting this.
I thought, it might have been fixed with the commit 4.2-630-g65e33c0
below , but it’s not.
Author: Nico Huber <nico.huber(a)secunet.com>
Date: Mon Dec 28 20:17:13 2015 +0100
x86: Align CBFS on top of ROM
Since the introduction of the new (interim?) master header, coreboot
searches the whole ROM for CBFS entries. Fix that by aligning it on top
of the ROM.
Do you know, which commit the commit message referred to?
Looking more into it, Nico’s commit was reverted in commit 4.2-673-
g12c55ed  and the logic reworked.
Author: Aaron Durbin <adurbin(a)chromium.org>
Date: Mon Jan 4 13:57:07 2016 -0600
Revert "x86: Align CBFS on top of ROM"
This reverts commit 65e33c08a9a88c52baaadaf515b9591856115a77.
This was the wrong logic to fix the master header.
If you have any suggestions, please tell me. Otherwise, I’d continue
trying to bisect this.
And unfortunately, I am unable to provide romstage messages, as I still
haven’t got the serial header for the board.
So if somebody else, Stefan, Martin, Kevin, could provide that, that
would be awesome.
Did you rebuild cbfstool that contains this patch?
It was the one I said fixed the
logic when you asked in https://review.coreboot.org/#/c/12824/
Additionally, there's also the comments I left in
that explained how that patch was
Please provide a hexdump snippet (hexdump -C image.rom) that shows the
"ORBC" section. That's the master header, and we can analyze if you
did indeed build w/ an updated cbfstool as well as determine if there
are other issues.