No, it would not be.
We cannot blindly (and dangerously) reprogram the DMA mode
of the drive without knowing what mode the IDE interface
chipset is trying to use. The two must match.
If the chipset is BIOS-configured for UDMA,
then we could break things big-time by selecting DMA at the drive..
The IDE driver already does the Most Sensible things by default,
leaving the chipset and drive settings as set-up by the BIOS.
If DMA fails, the IDE driver automatically falls back to PIO mode,
without loss of data or corruption of any sort.
There are NO current documented cases of disk corruption due to DMA
in the Linux IDE driver. If anyone thinks they know of such a case,
I'd be happy to investigate it .. but all such cases thus far have
been proven bogus.
I will not be updating the IDE driver again
until the linux/drivers/block/Config.in file
is restored to its pre-111 state.
-- email@example.com The Linux IDE guy
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html