Date: Thu, 21 Jul 2005 08:08:20 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: michael@staff.openaccess.org Cc: NKoch@demig.de, freebsd-small@freebsd.org, non_secure@yahoo.com Subject: Re: DMA disable for sandisk CF cards ? Message-ID: <20050721.080820.07020447.imp@bsdimp.com> In-Reply-To: <aff8f8006e7620113e0ba99103d9c000@staff.openaccess.org> References: <001e01c58dbe$f6739600$4801a8c0@ws-ew-3.W2KDEMIG> <20050721.020703.41710119.imp@bsdimp.com> <aff8f8006e7620113e0ba99103d9c000@staff.openaccess.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <aff8f8006e7620113e0ba99103d9c000@staff.openaccess.org>
Michael DeMan <michael@staff.openaccess.org> writes:
: I presume this would also work for non-booting devices too? Like our
: dev boxes where we burn cards and see numerous nasty log entries about
: device timeouts and sometimes the flashcard burn works, and other times
: it doesn't?
It works for non-boot devices. But for non-boot devices, you can also
use atacontrol. However, for a development box, I'd get a CF adapater
that groks DMA. If you are using an CF to PCMCIA adapter, then the
problem is something else. We usually see timeouts on CF cards that
have been static zapped in that case...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050721.080820.07020447.imp>