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