On Wed, Jun 24, 2009 at 10:46 AM, Myles Watson <[email protected]> wrote:
> Ward, > > At the point where it starts to get garbled, can you insert an endless loop > for a processor that isn't the BSP? Or insert a loop that prints the > processor's number in a loop. Just a sanity check. > > Thanks, > Myles > > Found CBFS 4f524243 Check normal/payload CBFS: follow chain: fff00000 + 28 + 10076 + align -> fff100a6 Check normal/coreboot_ram CBFS: follow chain: fff100a0 + 38 + 4a01c + align -> fff5a100 Check normal/coreboot_apc CBFS: follow chain: fff5a100 + 38 + 2be8 + align -> fff5cd20 Check fallback/payload CBFS: follow chain: fff5cd20 + 38 + 10076 + align -> fff6cdd0 Check fallback/corebot_ram Stage: load @ 1048576/696320 bytes, enter @ 100000 4a01c + : after memset 0on -stack variables at 001fedf8 and 001fee04 cbfs_decompress: algo: 0c8000 : uncompressed I'm done doing that by hand for a while :) So one processor loads coreboot_ram and jumps there, then another does memset on the same area so that it can load it? Thanks, Myles
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
