From: "Blue Swirl" <blauwirbel@gmail.com>
To: theburner1@yahoo.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Floppy: Remove Sense Interrupt Hack
Date: Sat, 20 Dec 2008 12:54:03 +0200 [thread overview]
Message-ID: <f43fc5580812200254r26a9d1abr6011cbc95fc74a7@mail.gmail.com> (raw)
In-Reply-To: <374626.12189.qm@web51107.mail.re2.yahoo.com>
On 12/19/08, Justin Chevrier <theburner1@yahoo.com> wrote:
>
>
>
> --- On Fri, 12/19/08, Blue Swirl <blauwirbel@gmail.com> wrote:
>
> > From: Blue Swirl <blauwirbel@gmail.com>
> > Subject: Re: [Qemu-devel] [PATCH] Floppy: Remove Sense Interrupt Hack
> > To: theburner1@yahoo.com, qemu-devel@nongnu.org
> > Date: Friday, December 19, 2008, 2:43 PM
>
> > On 12/18/08, Justin Chevrier <theburner1@yahoo.com>
> > wrote:
> > > Hey guys,
> > >
> > > I'm tracking down the next issue(s) with the
> > Openserver installation. The current issue is that during
> > installation when the installer tries to link the BLTD (eg.
> > SCSI drivers) drivers into the kernel it is unable to access
> > the floppy drive. After reviewing the debug logs it turns
> > out that the installer dosen't like the value being
> > returned by Sense Interrupt. The cause of this is a hack in
> > the Sense Interrupt code that always returns an OR'd
> > value based on FD_SR0_SEEK instead of the actual Status0
> > regsiter. The hack identifies that the floppy code is broken
> > with regard to Status0 and Read/Writes. Outside of setting
> > particular values in case of CRC errors/etc I can't
> > identify from datasheets what we should be doing. I've
> > tracked down what I believe is the original mailing list
> > post regarding this hack and it seems to be related to
> > Windows 2000 and higher OS's recognizing the floppy
> > drive. I applied the patch below and verified that
> > > detection/read/writes/formatting still work in
> > Windows XP SP2.
> > >
> > > Original post:
> > >
> > http://lists.gnu.org/archive/html/qemu-devel/2004-10/msg00076.html
> > >
> > > SVN change:
> > >
> > http://svn.savannah.gnu.org/viewvc?view=rev&root=qemu&revision=1118
> > >
> > > Having said the above does anyone know what the
> > comment in the hack is referencing? Is it still needed? If
> > so what needs to be done to eliminate it?
> > >
> > > If it's no longer needed I propose the patch
> > below.
> > >
> > > Justin
> > >
> > > Changelog:
> > >
> > > Remove Sense Interrupt hack
> > >
> > > Signed-off-by: Justin Chevrier
> > <theburner1@yahoo.com>
> >
> > It may be a hack, but if we remove it, Sparc64 refuses to
> > boot and
> > prints endlessly:
> > SENSEI c0 00
> > SENSEI c0 00
> > SENSEI c0 00
> > SENSEI c0 00
>
>
> Okay, thanks for the feedback!
>
> I'll start looking into what SPARC64 expects here.
The message is printed here:
http://tracker.coreboot.org/trac/openbios/browser/openbios-devel/drivers/floppy.c#L359
next prev parent reply other threads:[~2008-12-20 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:14 [Qemu-devel] [PATCH] Floppy: Remove Sense Interrupt Hack Justin Chevrier
2008-12-19 19:43 ` Blue Swirl
2008-12-19 21:41 ` Justin Chevrier
2008-12-20 10:54 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-23 18:02 Justin Chevrier
2008-12-23 18:13 ` Blue Swirl
2008-12-23 18:30 ` Blue Swirl
2008-12-23 19:43 ` Carl-Daniel Hailfinger
2008-12-23 19:58 ` Blue Swirl
2008-12-23 21:46 ` Carl-Daniel Hailfinger
2008-12-23 18:13 Justin Chevrier
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=f43fc5580812200254r26a9d1abr6011cbc95fc74a7@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).