On Wed, Feb 2 at 9:13, viresh kumar wrote:
On 02/01/2011 11:29 PM, Eric D. Mudama wrote:
On Tue, Feb 1 at 21:02, Viresh Kumar wrote:
I debugged it further and found that after data is transferred,
altstatus register is returning status 0xd0, which means ATA_BUSY.
I am not sure why this must be returned by card after data is transferred?
Did you wait for the interrupt? Or is this polling alt status
immediately after completing the data transfer?
I waited for this interrupt:
INTRQ_Int: This is the direct assignment of the CF/CF+ Interface pin 37 (INTRQ) when the
Interface is operating in TrueIDE Mode. This is the Interrupt from the Card.
The Software must read the ATA Status Register to find the source of Interrupt.
And i think that is sufficient enough.
Yes, should be. Do both alt status and regular status show this signature?
Possible there's some kind of hardware race condition, though IDE is
pretty much a "known" interface.
Just to get over this doubt, i will try place a small udelay after data is transferred
and before framework is communicated for successful xfer.
That's a good thing to try, wouldn't be the first time I've heard of
things like that being required.
--
Eric D. Mudama
edmudama@xxxxxxxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
