From owner-freebsd-doc Mon Dec 18 15: 4:15 2000 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 18 15:04:13 2000 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from relay.ultimanet.com (relay.ultimanet.com [205.179.129.1]) by hub.freebsd.org (Postfix) with ESMTP id A0B8D37B400 for ; Mon, 18 Dec 2000 15:04:13 -0800 (PST) Received: from Cloudfactory.ORG (cloudfactory.org [205.179.129.18]) by relay.ultimanet.com (8.9.3/8.9.3) with ESMTP id PAA14493 for ; Mon, 18 Dec 2000 15:22:52 -0800 Message-Id: <200012182322.PAA14493@relay.ultimanet.com> To: doc@freebsd.org Organization: Cloud Factory Collective X-Mailer: nmh 1.0.4 + mh-e Subject: kernelconfig-config.html: ATA_ENABLE_ATAPI_DMA Date: Mon, 18 Dec 2000 15:04:12 -0800 From: Randy Primeaux Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following entries are not clear to me, i.e. risk vs. benefit. I have UDMA33/66/100 devices, and am considering enabling ATA_ENABLE_ATAPI_DMA on a pci bus. While I could send this query to -questions, I'd like the response to be reflected in the Handbook. http://www.FreeBSD.org/handbook/kernelconfig-config.html options ATA_STATIC_ID #Static device numbering This makes the controller number static (like the old driver) or else the device numbers are dynamically allocated. #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices This enables DMA on the ATAPI device. Since many ATAPI devices claim to support DMA, but it does not actually work, this is turned off by default. -- Randy Primeaux randy@cloudfactory.org FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message