From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1J46eV-0001hS-9Q
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:28:23 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1J46eR-0001fa-OI
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:28:22 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1J46eR-0001fU-FZ
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:28:19 -0500
Received: from relay01.mx.bawue.net ([193.7.176.67])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <ths@networkno.de>) id 1J46eQ-0008CT-VO
	for qemu-devel@nongnu.org; Sun, 16 Dec 2007 22:28:19 -0500
Date: Mon, 17 Dec 2007 03:28:12 +0000
From: Thiemo Seufer <ths@networkno.de>
Subject: Re: [Qemu-devel] floppy disk
Message-ID: <20071217032811.GA17397@networkno.de>
References: <001301c84056$e0289420$01fea8c0@fys>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001301c84056$e0289420$01fea8c0@fys>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Benjamin David Lunt <fys@frontiernet.net>
Cc: qemu-devel@nongnu.org

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. :-)


Thiemo