From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: 2.6.32: Promise UDMA33 card refuses to work in UDMA mode
Date: Tue, 05 Jan 2010 05:04:42 -0500 [thread overview]
Message-ID: <4B430EBA.1030908@garzik.org> (raw)
In-Reply-To: <4B428FF5.7040702@gmail.com>
On 01/04/2010 08:03 PM, Robert Hancock wrote:
> rom ATA-8 APT:
>
> "HDMA0: Check_Status State: This state is entered when the host has
> written a DMA command to the device; when all data for the command has
> been transferred and nIEN is set to one; or when all data for the
> command has been transferred, nIEN is cleared zero, and INTRQ has been
> asserted.
>
> When in this state, the host shall read the device Status register. When
> entering this state from the HI4 state, the host shall wait 400 ns
> before reading the Status register. When entering this state from the
> HDMA1 state,
> the host shall wait one PIO transfer cycle time before reading the
> Status register. The wait may be accomplished by reading the Alternate
> Status register and ignoring the result."
Indeed... I had forgotten about that bit.
Jeff
next prev parent reply other threads:[~2010-01-05 10:04 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 18:13 2.6.32: Promise UDMA33 card refuses to work in UDMA mode Russell King
2009-12-24 21:54 ` Russell King
2010-01-03 0:23 ` Russell King
2010-01-03 3:08 ` Robert Hancock
2010-01-03 10:05 ` Russell King
2010-01-03 11:40 ` Alan Cox
2010-01-03 22:35 ` [PATCH] Fix Promise UDMA33 IDE driver (pdc202xx_old) Russell King
2010-01-04 19:14 ` Sergei Shtylyov
2010-01-05 6:26 ` David Miller
2010-01-05 17:49 ` Russell King
2010-01-05 17:52 ` Sergei Shtylyov
2010-01-03 23:46 ` 2.6.32: Promise UDMA33 card refuses to work in UDMA mode Russell King
2010-01-04 10:37 ` Alan Cox
2010-01-04 13:30 ` Russell King
2010-01-04 15:16 ` Alan Cox
2010-01-04 15:32 ` Jeff Garzik
2010-01-04 15:44 ` Russell King
2010-01-04 15:55 ` Alan Cox
2010-01-04 16:15 ` Russell King
2010-01-04 16:48 ` Jeff Garzik
2010-01-04 17:16 ` Sergei Shtylyov
2010-01-04 15:48 ` Alan Cox
2010-01-04 15:25 ` Jeff Garzik
2010-01-04 15:42 ` Russell King
2010-01-05 2:06 ` Robert Hancock
2010-01-05 11:25 ` Alan Cox
2010-01-05 13:00 ` Jeff Garzik
2010-01-05 13:37 ` Alan Cox
2010-01-05 13:11 ` Jeff Garzik
2010-01-04 15:46 ` Alan Cox
2010-01-04 16:32 ` Jeff Garzik
2010-01-04 17:02 ` Alan Cox
2010-01-04 17:27 ` Jeff Garzik
2010-01-04 17:30 ` Russell King
2010-01-04 18:03 ` Jeff Garzik
2010-01-04 18:06 ` Russell King
2010-01-04 18:35 ` Jeff Garzik
2010-01-04 17:38 ` Alan Cox
2010-01-04 18:07 ` Jeff Garzik
2010-01-04 18:29 ` Jeff Garzik
2010-01-04 16:31 ` Bartlomiej Zolnierkiewicz
2010-01-04 17:28 ` Russell King
2010-01-04 17:39 ` Alan Cox
2010-01-04 17:46 ` Russell King
2010-01-04 18:20 ` Alan Cox
2010-01-04 17:49 ` Bartlomiej Zolnierkiewicz
2010-01-05 1:03 ` Robert Hancock
2010-01-05 10:04 ` Jeff Garzik [this message]
2010-01-05 17:44 ` Russell King
2010-01-06 0:30 ` Robert Hancock
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=4B430EBA.1030908@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.