Hello, I wrote:
+ * stoppng and restarting the DMA, we'll let the hardware do
it. If the
stopping
+ * DMA is really stopped early due to an error condition, a later
I'm not sure which error condition is meant here: ERR=1 in the
status register, some internal DMA error, both?
+ * timeout will force us to stop.
Sigh... So any command error will result in a timeout. I wonder
what hardware genius decided that CF doesn't need an IRQ...
Ah, I forgot thet libata should be supporting polling mode, so should
handle ERR=1 case. In this case the comment about the timeout
contradicts your words about an interrupt being generated on DMA error.
So, Octeon DMA can actually generate an error interrupt?
MBR, Sergei
--
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
