From: "Blue Swirl" <blauwirbel@gmail.com>
To: theburner1@yahoo.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Floppy: Properly handle Sense Interrupt Status after FDC Reset
Date: Tue, 6 Jan 2009 17:35:32 +0200 [thread overview]
Message-ID: <f43fc5580901060735m52b13694r299dab9c464d59c5@mail.gmail.com> (raw)
In-Reply-To: <433254.27767.qm@web51101.mail.re2.yahoo.com>
On 1/6/09, Justin Chevrier <theburner1@yahoo.com> wrote:
> Attached is a patch that changes how the emulated floppy controller replies to Sense Interrupt Status commands immediately after a controller reset. The specs state that after a Reset the 82078 goes into polling mode which needs four Sense Interrupt Status commands to be issued afterwards to clear the status of each drive. Currently we always respond to Sense Interrupt Status with a SEEK END instead of POLLING. This causes a problem with the SCO Openserver installer which is expects a POLLING state after reset. This patch returns a POLLING status for four Sense Interrupt Status requests immediately after a controller reset. This approach mirrors the way Bochs handles this situation. With the attached patch applied Openserver gets further when trying to load storage drivers from the floppy disk (blocked by another issue, patch on its way). I have successfully tested the floppy drive on the following OSs after applying this patch: Windows 98, Windows XP
> SP2, Linux x86 (SysRescCD 1.1.3 and Ubuntu 8.10).
>
> Justin
>
> Changelog:
>
> Properly handle Sense Interrupt Status after FDC Reset
>
> Signed-off-by: Justin Chevrier <theburner1@yahoo.com>
OK for Sparc.
prev parent reply other threads:[~2009-01-06 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 3:15 [Qemu-devel] [PATCH] Floppy: Properly handle Sense Interrupt Status after FDC Reset Justin Chevrier
2009-01-06 15:35 ` Blue Swirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f43fc5580901060735m52b13694r299dab9c464d59c5@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=theburner1@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).