From: Kevin Wolf <kwolf@redhat.com>
To: Pavel Hrdina <phrdina@redhat.com>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] fdc: fix media change detection for windows
Date: Tue, 05 Jun 2012 16:02:20 +0200 [thread overview]
Message-ID: <4FCE116C.4050008@redhat.com> (raw)
In-Reply-To: <9349989e1c2f12d5d6bc00089efdb7947fdf8dac.1338903679.git.phrdina@redhat.com>
Am 05.06.2012 15:48, schrieb Pavel Hrdina:
> The windows uses 'READ' command at the start of instalation. We have to
> also check the 'media_change' bit in the 'fd_seek'.
>
> Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
Can you explain the scenario in more detail? What is Windows trying and
why should it fail? What is happening today?
> ---
> hw/fdc.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/hw/fdc.c b/hw/fdc.c
> index 30d34e3..70b0c00 100644
> --- a/hw/fdc.c
> +++ b/hw/fdc.c
> @@ -128,7 +128,8 @@ static int fd_seek(FDrive *drv, uint8_t head, uint8_t track, uint8_t sect,
> int ret;
>
> if (track > drv->max_track ||
> - (head != 0 && (drv->flags & FDISK_DBL_SIDES) == 0)) {
> + (head != 0 && (drv->flags & FDISK_DBL_SIDES) == 0) ||
> + drv->media_changed) {
> FLOPPY_DPRINTF("try to read %d %02x %02x (max=%d %d %02x %02x)\n",
> head, track, sect, 1,
> (drv->flags & FDISK_DBL_SIDES) == 0 ? 0 : 1,
Context: Next thing in the code is an error return.
This looks wrong to me. drv->media_changed is also true when a new
floppy has been inserted, but there was no step pulse yet. Is there any
reason why an fd_seek() should fail when a floppy is present?
Last, but not least: Any floppy fixes should come with qtest cases.
Kevin
next prev parent reply other threads:[~2012-06-05 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 13:48 [Qemu-devel] [PATCH] fdc: fix media change detection for windows Pavel Hrdina
2012-06-05 14:02 ` Kevin Wolf [this message]
2012-06-05 14:30 ` Pavel Hrdina
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=4FCE116C.4050008@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=mtosatti@redhat.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).