From: Alexander Graf <agraf@suse.de>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] AHCI / Sata port initial error status
Date: Thu, 03 Jul 2014 13:57:25 +0200 [thread overview]
Message-ID: <53B54525.1020906@suse.de> (raw)
In-Reply-To: <53B1B717.6070205@redhat.com>
On 30.06.14 21:14, John Snow wrote:
> I am in the process of writing a series of AHCI tests (for q35) that
> compare the written specifications against what the current device
> emulation actually does, and I was curious about this bit instead of
> ahci.c, in ahci_reset_port:
>
> ide_state->error = 1;
>
> What does this error signify, exactly, and why is it set by default on
> ports with a device attached? It trickles up inside of the PxTFD.ERR
> byte in the HBA as well as showing up in the initial Register D2H FIS
> after the PxCMD.FRE bit is set.
I honestly don't remember :). We do unset the error bit once we get the
first working command though.
Alex
prev parent reply other threads:[~2014-07-03 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 19:14 [Qemu-devel] AHCI / Sata port initial error status John Snow
2014-07-03 11:57 ` Alexander Graf [this message]
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=53B54525.1020906@suse.de \
--to=agraf@suse.de \
--cc=jsnow@redhat.com \
--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).