From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J46p4-0006S2-MW for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:39:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J46p0-0006PA-Ul for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:39:17 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J46p0-0006Ow-Ng for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:39:14 -0500 Received: from mx11.roch.ny.frontiernet.net ([66.133.183.238]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J46p0-00019c-BT for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:39:14 -0500 Message-ID: <001001c8405e$64faa330$01fea8c0@fys> From: "Benjamin David Lunt" References: <001301c84056$e0289420$01fea8c0@fys> <20071217032811.GA17397@networkno.de> Subject: Re: [Qemu-devel] floppy disk Date: Sun, 16 Dec 2007 20:39:11 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Thiemo Seufer Cc: qemu-devel@nongnu.org ----- Original Message ----- From: "Thiemo Seufer" To: "Benjamin David Lunt" Cc: Sent: Sunday, December 16, 2007 8:28 PM Subject: Re: [Qemu-devel] floppy disk > Benjamin David Lunt wrote: >> Hi everyone, >> >> I only recently have started to use QEmu due to a request >> on the alt.os.development usenet group. My OS was not working >> on QEmu due to it would not recognize the (emulated) floppy. >> >> After a lot of testing, QEmu does not return the correct >> values for a Sense Interrupt command and the Status 0 byte. >> >> After looking over fdc.cc, someone has placed a hack write >> where it should return these values. >> >> I am just wondering if this hack is temporary or if it will >> be committed as code. > > That's the current state of the code in CVS. > >> For a more detailed description, QEmu returns the value >> 0x20 while Bochs, VMware, and real hardware return the >> values 0xC0, 0xC1, 0xC2, and 0xC3, for each drive 1 - 4 >> respectively. >> >> I am asking for more information on this subject. > > The interrupt status handling in QEMU's FDC emulation looks bogus > to me, patches to fix it are welcome. :-) Hi Thiemo, (smile) I may have a chance to do so in the near future. If I do, I will post it here or find the correct way to post a patch. Thanks, Ben