From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J89Jp-0006OL-9o for qemu-devel@nongnu.org; Fri, 28 Dec 2007 02:07:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J89Jn-0006NK-CC for qemu-devel@nongnu.org; Fri, 28 Dec 2007 02:07:44 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J89Jn-0006NF-18 for qemu-devel@nongnu.org; Fri, 28 Dec 2007 02:07:43 -0500 Received: from wa-out-1112.google.com ([209.85.146.178]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J89Jm-000763-MX for qemu-devel@nongnu.org; Fri, 28 Dec 2007 02:07:42 -0500 Received: by wa-out-1112.google.com with SMTP id k22so5718060waf.18 for ; Thu, 27 Dec 2007 23:07:41 -0800 (PST) Message-ID: Date: Fri, 28 Dec 2007 16:07:40 +0900 From: "Jun Koi" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Qemu-devel] Entry point of BIOS Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, I am wondering how qemu can find exactly where is the entry point of BIOS? Of course it is at offset 0xfff0 of BIOS, starting from the base address of BIOS. It is easy to understand how it works with the BIOS legacy. However, if we use the BIOS-latest, which is made by prepending the rombios32.bin in front of BIOS-legacy, how qemu is still able to find the same entry point at 0xfff0 (which is actually at 0x10000 + 0xfff0 from the base address now). This confuses me, and I dont find anything from source code that does this. Or I missed something .... Many thanks, Jun