Re: Is there still sufficient reason for hw.ata.atapi_dma being 0 by default?

From: Maxime Henrion (mux_at_freebsd.org)
Date: 07/30/04

  • Next message: Thomas David Rivers: "Re: about the gcc 3.4.x problems"
    Date: Fri, 30 Jul 2004 14:17:13 +0200
    To: Maxim Sobolev <sobomax@portaone.com>
    
    

    Maxim Sobolev wrote:
    > Since high-speed CD-RW/DVD-RW recorders (32x - 52x) are commodity now
    > IMO it makes sense to review hw.ata.atapi_dma default of 0, since
    > apparently PIO mode can't support necessary sustained data transfer
    > rates anymore. For example I had had problems burning RWs on 16-24x with
    > several drives in PIO mode, which gone when I've switched to DMA.
    >
    > I easily imagine newbies who make a conclusion that "FreeBSD sucks"
    > after installing FreeBSD and finding that they can't burn CDs, while
    > other operating system do it without any problems.

    I think it should be enabled by default when the DMA mode of the ATAPI
    device is UDMA33 or higher, not when it's WDMA2. The atapi_dma sysctl
    is off by default to guard against buggy ATAPI devices which are
    incorrectly reporting themselves as being able to do DMA, however
    I think this mostly applies to old devices, which won't do UDMA33 or
    higher. Soren would know better than me though.

    Cheers,
    Maxime

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


  • Next message: Thomas David Rivers: "Re: about the gcc 3.4.x problems"

    Relevant Pages

    • Re: Is there still sufficient reason for hw.ata.atapi_dma being 0 by default?
      ... > several drives in PIO mode, which gone when I've switched to DMA. ... Hmm, things are still messy, but most drives that support UDMA33 can do ... ATAPI dma. ...
      (freebsd-current)
    • Re: regression in ata/atapi wrt dma?
      ... > claims DMA but really doesn't work. ... -ATAPI devices are set to PIO mode by default because severe DMA problems are ... -common even if the device capabilities indicate support. ... +ATAPI devices are set to DMA mode only if they claim to support at least UDMA33. ...
      (freebsd-current)
    • Is there still sufficient reason for hw.ata.atapi_dma being 0 by default?
      ... apparently PIO mode can't support necessary sustained data transfer ... For example I had had problems burning RWs on 16-24x with ... several drives in PIO mode, which gone when I've switched to DMA. ... I easily imagine newbies who make a conclusion that "FreeBSD sucks" ...
      (freebsd-current)
    • Re: Is there still sufficient reason for hw.ata.atapi_dma being 0 by default?
      ... For example I had had problems burning RWs on 16-24x with ... > several drives in PIO mode, which gone when I've switched to DMA. ... Funny, I have a cheap drive that I had problems with when using DMA, ...
      (freebsd-current)
    • Re: SEAGATE forced PIO instead of UDMA mode
      ... primary master device. ... still the same results under Windows. ... way until you fix the reason its decided to turn DMA off. ... fresh on the new seagate but still its PIO mode. ...
      (comp.sys.ibm.pc.hardware.storage)