From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N8TDt-0005D3-O9 for qemu-devel@nongnu.org; Thu, 12 Nov 2009 01:32:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N8TDp-00058d-U3 for qemu-devel@nongnu.org; Thu, 12 Nov 2009 01:32:01 -0500 Received: from [199.232.76.173] (port=50882 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8TDp-00058B-KZ for qemu-devel@nongnu.org; Thu, 12 Nov 2009 01:31:57 -0500 Received: from mail-px0-f197.google.com ([209.85.216.197]:45585) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N8TDp-0004hB-9n for qemu-devel@nongnu.org; Thu, 12 Nov 2009 01:31:57 -0500 Received: by pxi35 with SMTP id 35so1352930pxi.18 for ; Wed, 11 Nov 2009 22:31:56 -0800 (PST) MIME-Version: 1.0 Date: Thu, 12 Nov 2009 14:31:55 +0800 Message-ID: <6021f4870911112231j1a78010fsd721a1dec70c124e@mail.gmail.com> From: Aditya Agarwal Content-Type: multipart/alternative; boundary=00504502caf81c4628047826b3c4 Subject: [Qemu-devel] Handling Bios Interrupts List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --00504502caf81c4628047826b3c4 Content-Type: text/plain; charset=ISO-8859-1 How or which section of the QEMU source is actually handling BIOS interrupt call, I have written a new user interrupt 0x79 in BIOS.BIN, but I need to ask QEMU to purposely invoke INT 0x79 call, where this ISR will write some byte info into BDA/BIOS DATA AREA. --00504502caf81c4628047826b3c4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable How or which section of the QEMU source is actually handling BIOS interrupt= call, I have written a
new user interrupt 0x79 in BIOS.BIN, but I need = to ask QEMU to purposely invoke INT 0x79 call,
where this ISR will write= some byte info into BDA/BIOS DATA AREA.
--00504502caf81c4628047826b3c4--