[coreboot] qemu, v2, latest

Myles Watson mylesgw at gmail.com
Tue May 12 19:37:49 CEST 2009

On Tue, May 12, 2009 at 10:12 AM, ron minnich <rminnich at gmail.com> wrote:
> On Tue, May 12, 2009 at 8:56 AM, Myles Watson <mylesgw at gmail.com> wrote:
>>> Payload is overwriting Coreboot tables.
>> I don't see this line in mine.  Could you try HAVE_LOW_TABLES=0 and see if
>> that fixes it for you?  If so we can try to debug why having both doesn't
>> work.  If not we can compare payloads.  My entry point is different than
>> yours too.
> oops, I was not up to date on this one. Now the high tables are at
> Writing high table forward entry at 0x00000500
> Wrote coreboot table at: 00000500 - 00000518  checksum f3df
> New low_table_end: 0x00000500
> Now going to write high coreboot table at 0x03ff0800
> rom_table_end = 0x03ff0800
> Adjust low_table_end from 0x00000500 to 0x00001000
> Adjust rom_table_end from 0x03ff0800 to 0x04000000
> Adding high table area
> Wrote coreboot table at: 03ff0800 - 03ff0e8c  checksum 1a86
> which makes more sense. Still triple faulting however.
> I'll just have coreboot dump the first 32 bytes of memory at entry
> point to make sure it's what I think it is.
> If you can test latest coreboot with latest qemu I'd be interested.
It triple faults for me too.  I was using 0.9.1, and I downloaded 0.10.4.

> I have xxd'ed the coreboot rom and it certainly appears the data is in
> there correctly.
It looks like a qemu change.


More information about the coreboot mailing list