From: bacam@z273.org.uk (Brian Campbell)
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Running Plan9
Date: Thu, 2 Dec 2004 21:30:07 +0000 [thread overview]
Message-ID: <20041202213007.GA3650@z273.org.uk> (raw)
In-Reply-To: <20041202095125.GA6962@tuxedo.skovlyporten.dk>
On Thu, Dec 02, 2004 at 10:51:26AM +0100, Lars Munch wrote:
> On Wed, Dec 01, 2004 at 10:32:53PM +0000, Brian Campbell wrote:
> >
> > Adding some very shoddy (and almost certainly wrong) support for
> > WIN_DIAGNOSE to ide_ioport_write in hw/ide.c was enough to get it to boot
> > and run the live version. Is anyone likely to provide a proper
> > implementation? I'd do it myself, but the (draft) ATA specs I had a look
> > through appeared to have some oddities I'd rather not have to deal with,
> > given that I've never done any ATA work before.
>
> I had the same problem when I tried to get the ide driver going in
> RTEMS, since it also depends on WIN_DIAGNOSE. I also added quick version
> of the WIN_DIAGNOSE command (just setting error register to 01h) and
> RTEMS found the disc.
>
> I just looked at the ATA specs. What oddities are you referring to?
The draft I looked at (d1410r3b ATA/ATAPI-6 revision 3b) has a section
on the "EXECUTE DEVICE DIAGNOSTIC command protocol", with various state
diagrams and timing information. The problem is that I've no idea if
this stuff would even be visible from the software's point of view, and
if it is, whether it's worth emulating it.
Cheers,
Brian
next prev parent reply other threads:[~2004-12-02 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 22:32 [Qemu-devel] Running Plan9 Brian Campbell
2004-12-02 9:51 ` Lars Munch
2004-12-02 21:30 ` Brian Campbell [this message]
2004-12-02 20:18 ` Fabrice Bellard
2004-12-02 21:52 ` Brian Campbell
2004-12-04 23:50 ` Lars Munch
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=20041202213007.GA3650@z273.org.uk \
--to=bacam@z273.org.uk \
--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).