-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel James wrote: > Hi Quentin, > >>>> Is this important? >>> I don't think so - we already set DMA on by default. sudo hdparm >>> /dev/hda (or other drive device name) should confirm this. >> That's the thing... This is a kernel I built myself to enable the >> stable firewire stack for amd64. The rt13 kernel. I cannot find the >> setting for enabling DMA ;-) > > I think it's probably redundant now, the IDE stack in recent kernels may > have done away with the option. It's hard to imagine why you wouldn't > want DMA enabled. > I do not have any PATA drives any more, but here are all the DMA options in my .config:
$ grep DMA .config CONFIG_ZONE_DMA=y CONFIG_GENERIC_ISA_DMA=y CONFIG_ZONE_DMA32=y CONFIG_HAVE_DMA_API_DEBUG=y # CONFIG_HAVE_GENERIC_DMA_COHERENT is not set CONFIG_ZONE_DMA_FLAG=1 # CONFIG_DMAR is not set CONFIG_ISA_DMA_API=y CONFIG_SCSI_DMA=y CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1 CONFIG_PDC_ADMA=m # CONFIG_PATA_HPT3X3_DMA is not set # CONFIG_PATA_OPTIDMA is not set # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_B43LEGACY_DMA=y CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y # CONFIG_B43LEGACY_DMA_MODE is not set CONFIG_CARDMAN_4000=m CONFIG_CARDMAN_4040=m CONFIG_VIDEOBUF_DMA_SG=m CONFIG_DMADEVICES=y # DMA Devices CONFIG_INTEL_IOATDMA=m CONFIG_DMA_ENGINE=y # DMA Clients CONFIG_NET_DMA=y # CONFIG_DMATEST is not set # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set # CONFIG_DMA_API_DEBUG is not set CONFIG_HAS_DMA=y -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkolWoMACgkQwRXgH3rKGfPD5wCfU6miO3P2w5KLybq+8yE8RmGK 3WAAoLIo391oR396bxgd47Z2Z39xBFa2 =rGGo -----END PGP SIGNATURE----- _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
