From: Kevin Wolf <kwolf@redhat.com>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 04/10] fdc: emulate stepping 0
Date: Mon, 16 Jan 2012 10:54:27 +0100 [thread overview]
Message-ID: <4F13F3D3.9010200@redhat.com> (raw)
In-Reply-To: <1326613915-3282-5-git-send-email-hpoussin@reactos.org>
Am 15.01.2012 08:51, schrieb Hervé Poussineau:
> Stepping 1 (S82078B) is not fully i82078 compatible, so better stick to initial revision
>
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
> ---
> hw/fdc.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/fdc.c b/hw/fdc.c
> index bedaeca..0e167f8 100644
> --- a/hw/fdc.c
> +++ b/hw/fdc.c
> @@ -1385,7 +1385,7 @@ static void fdctrl_handle_version(FDCtrl *fdctrl, int direction)
>
> static void fdctrl_handle_partid(FDCtrl *fdctrl, int direction)
> {
> - fdctrl->fifo[0] = 0x41; /* Stepping 1 */
> + fdctrl->fifo[0] = 0x01; /* Stepping 0 */
> fdctrl_set_fifo(fdctrl, 1, 0);
> }
>
Hm, this is the kind of change that I'm hesitant to make because I don't
understand the implications. Can you give some more details what is
fixed by this and why you think it's harmless for currently working OSes?
My spec says this:
6 3 14 PART ID COMMAND
This command can be used to identify the floppy
disk controller as an enhanced controller The first
stepping of the 82078 (all 44 pin versions) will yield
0x41 in the result phase of this command Any future
enhancements on these parts will be denoted by the
5 LSBs (0x01 to 0x1F)
It doesn't even define what 0x01 would mean.
Kevin
next prev parent reply other threads:[~2012-01-16 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 7:51 [Qemu-devel] [PATCH v2 00/10] Misc fixes for floppy emulation Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 01/10] fdc: take side count into account Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 02/10] fdc: set busy bit when starting a command Hervé Poussineau
2012-01-16 9:33 ` Kevin Wolf
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 03/10] fdc: most control commands do not generate interrupts Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 04/10] fdc: emulate stepping 0 Hervé Poussineau
2012-01-16 9:54 ` Kevin Wolf [this message]
2012-01-23 7:58 ` Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 05/10] fdc: handle read-only floppies (abort early on write commands) Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 06/10] fdc: add CCR (Configuration Control Register) write register Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 07/10] block: add a transfer rate for floppy types Hervé Poussineau
2012-01-16 10:18 ` Kevin Wolf
2012-01-21 19:02 ` Blue Swirl
2012-01-23 8:51 ` Kevin Wolf
2012-01-23 16:56 ` Blue Swirl
2012-01-27 8:33 ` Markus Armbruster
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 08/10] fdc: check if media rate is correct before doing any transfer Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 09/10] fdc: fix seek command, which shouldn't check tracks Hervé Poussineau
2012-01-16 10:32 ` Kevin Wolf
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 10/10] fdc: DIR (Digital Input Register) should return status of current drive Hervé Poussineau
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=4F13F3D3.9010200@redhat.com \
--to=kwolf@redhat.com \
--cc=hpoussin@reactos.org \
--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).