From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc/patch] libata -- port configurable delays
Date: Sat, 14 May 2005 22:11:38 +0100 [thread overview]
Message-ID: <1116105095.20545.55.camel@localhost.localdomain> (raw)
In-Reply-To: <42853687.1050402@pobox.com>
On Sad, 2005-05-14 at 00:21, Jeff Garzik wrote:
> > If your chipset implements the 400nS lockout in hardware it certainly
> > seems to make sense. Nice to know someone has put it in hardware
>
> No, it's just mostly irrelevant under SATA.
libata is for PATA devices too.
> The ATA registers are transmitted to the device in a single packet,
> called a FIS, when the Command or Device Control register is written.
>
> When the device updates its status, or completes a command, it sends a
> FIS from device to controller, instructing the controller to update its
> cached copy of the Status register.
The controller in ATA style behaviour isn't required to have the status
register valid at the point the FIS is written. It probably does but it
isn't required.
next prev parent reply other threads:[~2005-05-14 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 18:58 [rfc/patch] libata -- port configurable delays Benjamin LaHaise
2005-05-13 19:13 ` Jeff Garzik
2005-05-13 20:03 ` Benjamin LaHaise
2005-05-13 21:52 ` Alan Cox
2005-05-13 23:07 ` Jeff Garzik
2005-05-14 1:51 ` Mark Lord
2005-05-13 19:17 ` Jeff Garzik
2005-05-13 21:20 ` Alan Cox
2005-05-13 23:21 ` Jeff Garzik
2005-05-14 21:11 ` Alan Cox [this message]
2005-05-14 21:47 ` Jeff Garzik
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=1116105095.20545.55.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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).