first, could you please adhere to the netiquette ? Please configure
the Yahoo Web client to send plain text messages and no HTML messages.
Also please use interleaved style for replying.
Am Dienstag, den 12.11.2013, 15:58 -0800 schrieb Jonathan Sturges:
I haven't made much progress. I've had a few
issues getting an
updated SeaBIOS installed as a payload. There are only 2 selections
for SeaBIOS in coreboot's menuconfig: 184.108.40.206 and "master." I
selected "master" this time and seem to get version
"rel-1.7.3-91-gc21dce3-20131004_231309", which looks like it's from
early October. However, same results with this release. Should 1.7.3
be good enough?
The »-91« means that 91 commits have been applied an top of tag 1.7.3.
So it is indeed latest master when you build it.
$ git show --format=fuller --stat c21dce3
Author: Kevin O'Connor <kevin(a)koconnor.net>
AuthorDate: Sat Oct 26 11:56:24 2013 -0400
Commit: Kevin O'Connor <kevin(a)koconnor.net>
CommitDate: Sat Oct 26 11:56:24 2013 -0400
Minor - eliminate the SET_GLOBAL macro.
Remove the SET_GLOBAL macro - it is no longer used and since it was
only available in "32bit flat" mode it does not have much use.
Signed-off-by: Kevin O'Connor <kevin(a)koconnor.net>
README | 21 ++++++++++-----------
src/biosvar.h | 4 ----
2 files changed, 10 insertions(+), 15 deletions(-)
I next checked out and built a separate SeaBIOS ELF
image, so I could
have the absolute latest SeaBIOS AND set debug to 8 (Coreboot doesn't
seem to have the SeaBIOS debug level available via menuconfig). But,
I've been unable to get Coreboot to build if I select an ELF payload
via menuconfig and supply the path to my bios.bin.elf; it only builds
when selecting SeaBIOS as the payload directly via menuconfig.
Could you please send a report with the build logs to the coreboot
mailing list? That would be great.