On Tue, Feb 26, 2002 at 01:37:55AM -0800, Andre Hedrick wrote:
[...]
| The real solution for distros is to wrapper the dma_capable flags in the
| module cores in 2.4 under the disk_only. Also not setting
| CONFIG_IDEDMA_AUTO will help but you are not permitted to invoke
|
| echo using_dma:1 > /proc/ide/hda/settings
I noticed that "hdparm -d1 /dev/hda" timed out three times and reverted
to PIO in my case, with DMA enabled but autoDMA disabled. So does DMA
support have to be on at boot and is only allowed to be disabled, not
enabled?
If so, ide=dma is the proper solution for trusted boards, but it would
be nice if the /proc or hdparm interfaces worked reliably for enabling
DMA.
So what does this say about the autoDMA issue that I'm seeing? For me,
the best of both worlds is to have DMA enabled, but off by default and
capable of being enabled from userspace (and kernel command line, less
usefully).
Thanks,
-- Ken. brownfld@irridia.com| One of the issues to be address is a test for transfer modes, but have to | many other issues to address w/ clients to deal with distro issues. | | Cheers, | | Andre Hedrick | Linux Disk Certification Project Linux ATA Development - 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/
This archive was generated by hypermail 2b29 : Thu Feb 28 2002 - 21:00:26 EST