qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Benjamin David Lunt" <fys@frontiernet.net>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] floppy disk
Date: Sun, 16 Dec 2007 20:39:11 -0700	[thread overview]
Message-ID: <001001c8405e$64faa330$01fea8c0@fys> (raw)
In-Reply-To: 20071217032811.GA17397@networkno.de


----- Original Message ----- 
From: "Thiemo Seufer" <ths@networkno.de>
To: "Benjamin David Lunt" <fys@frontiernet.net>
Cc: <qemu-devel@nongnu.org>
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

  reply	other threads:[~2007-12-17  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  2:45 [Qemu-devel] floppy disk Benjamin David Lunt
2007-12-17  3:28 ` Thiemo Seufer
2007-12-17  3:39   ` Benjamin David Lunt [this message]
2007-12-17 14:40   ` J. Mayer
2007-12-18  0:53     ` Benjamin David Lunt

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='001001c8405e$64faa330$01fea8c0@fys' \
    --to=fys@frontiernet.net \
    --cc=qemu-devel@nongnu.org \
    --cc=ths@networkno.de \
    /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).