From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56459 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEd1h-0004MV-9l for qemu-devel@nongnu.org; Wed, 19 May 2010 02:45:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEd1f-0002Lh-PC for qemu-devel@nongnu.org; Wed, 19 May 2010 02:45:09 -0400 Received: from mail-wy0-f173.google.com ([74.125.82.173]:41044) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEd1f-0002LZ-Jk for qemu-devel@nongnu.org; Wed, 19 May 2010 02:45:07 -0400 Received: by wyb39 with SMTP id 39so2104320wyb.4 for ; Tue, 18 May 2010 23:45:05 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 18 May 2010 23:45:05 -0700 Message-ID: From: Ed Swierk Content-Type: multipart/mixed; boundary=0016e6daa93d51285c0486eccc0d Subject: [Qemu-devel] [Qemu] [PATCH] Allow booting large Coreboot image as BIOS List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Coreboot , qemu-devel@nongnu.org --0016e6daa93d51285c0486eccc0d Content-Type: text/plain; charset=ISO-8859-1 When I build a 1024-kB Coreboot image (emulation/qemu-x86 mainboard), qemu goes into a loop, resetting just after the "Jumping to boot code" message. This can be avoided by removing the "| IO_MEM_ROM" from the call to cpu_register_physical_memory(0x100000 - isa_bios_size, ...) call in pc_memory_init(). The next problem I hit is the complaint "ERROR: No valid CBFS header found! Maybe the ROM isn't entirely mapped yet?". I can work around this by allocating a separate chunk of RAM for the top 128 kB of the BIOS image in ISA space and copying it rather than mapping it from the full ROM image. Both of these changes are the result of random hacking rather than any real understanding of the issues involved. I'd appreciate any better ideas. Signed-off-by: Ed Swierk --- hw/pc.c | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) --0016e6daa93d51285c0486eccc0d Content-Type: text/x-patch; charset=US-ASCII; name="0001-Current-qemu-has-problems-booting-with-Coreboot-in-p.patch" Content-Disposition: attachment; filename="0001-Current-qemu-has-problems-booting-with-Coreboot-in-p.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: 0.1 ZGlmZiAtLWdpdCBhL2h3L3BjLmMgYi9ody9wYy5jCmluZGV4IDIwZGM3ZmQuLjg4NDc4ZTcgMTAw NjQ0Ci0tLSBhL2h3L3BjLmMKKysrIGIvaHcvcGMuYwpAQCAtODgwLDcgKzg4MCwxMCBAQCB2b2lk IHBjX21lbW9yeV9pbml0KHJhbV9hZGRyX3QgcmFtX3NpemUsCiAgICAgICAgIGlzYV9iaW9zX3Np emUgPSAxMjggKiAxMDI0OwogICAgIGNwdV9yZWdpc3Rlcl9waHlzaWNhbF9tZW1vcnkoMHgxMDAw MDAgLSBpc2FfYmlvc19zaXplLAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgaXNh X2Jpb3Nfc2l6ZSwKLSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIChiaW9zX29mZnNl dCArIGJpb3Nfc2l6ZSAtIGlzYV9iaW9zX3NpemUpIHwgSU9fTUVNX1JPTSk7CisgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICBxZW11X3JhbV9hbGxvYyhpc2FfYmlvc19zaXplKSk7Cisg ICAgY3B1X3BoeXNpY2FsX21lbW9yeV93cml0ZV9yb20oMHgxMDAwMDAgLSBpc2FfYmlvc19zaXpl LAorICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHFlbXVfZ2V0X3JhbV9wdHIoYmlv c19vZmZzZXQgKyBiaW9zX3NpemUgLSBpc2FfYmlvc19zaXplKSwKKyAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICBpc2FfYmlvc19zaXplKTsKIAogICAgIG9wdGlvbl9yb21fb2Zmc2V0 ID0gcWVtdV9yYW1fYWxsb2MoUENfUk9NX1NJWkUpOwogICAgIGNwdV9yZWdpc3Rlcl9waHlzaWNh bF9tZW1vcnkoUENfUk9NX01JTl9WR0EsIFBDX1JPTV9TSVpFLCBvcHRpb25fcm9tX29mZnNldCk7 Cg== --0016e6daa93d51285c0486eccc0d--