Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Mar 2003 18:28:38 +0100 (CET)
From:      Soeren Schmidt <sos@spider.deepcore.dk>
To:        The Anarcat <anarcat@anarcat.ath.cx>
Cc:        Kevin Oberman <oberman@es.net>, Don <don@calis.blacksun.org>, Craig Reyenga <creyenga@connectmail.carleton.ca>, freebsd-current@FreeBSD.ORG
Subject:   Re: Broken DMA devices
Message-ID:  <200303251728.h2PHSdWt074651@spider.deepcore.dk>
In-Reply-To: <20030325161253.GA600@lenny.anarcat.ath.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
It seems The Anarcat wrote:
> On Tue Mar 25, 2003 at 08:16:28AM +0100, Soeren Schmidt wrote:
> > It seems The Anarcat wrote:
> > > Can't the ata drivers detect that condition or recognize the set of
> > > drives that are broken instead of penalizing everyone else?
> > 
> > ATAPI DMA is more likely to be broken than to be working, it is a 
> > function of both controller chip and device, in some situations even
> > a function of what master/slave device combo we have..
> > 
> > There is a reason that almost all OS's out there has it disabled as default :)
> 
> Thanks for those precisions... This could be a FAQ, pertaining also to
> how to enable it.
> 
> So it's enabled system-wide? Can't it be done at the bus or device
> level?

You can set the transfer mode of any ATA/ATAPI device with atacontrol...

-Søren

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303251728.h2PHSdWt074651>