> The driver pulled your system back into safe data io ranges.
> Either your cable routing is poor, your power supply is marginal, possible
> but not likely (hardware combination does not like the odd or even cable
> grounding setup), regardless it did the correct thing.
>
> The problem is a feature to prevent the driver from dropping out of DMA
> to PIO when it is better to down grade the transfer rate.
>
> The next issue is whether your ATAPI is in DMA, and it should not be.
> The driver core does not use split dma engines yet.
I just tried connecting it to a cmd646 controller. It runs at full speed
but no dma because of cmd bugs. Is there a problem with the new pdc202xx
driver in 2.4.19 or is it somehow my fault?
-- Måns Rullgård mru@users.sf.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/