From 6d3a461a4f20776be1a83de2eada39cb152efd48 Mon Sep 17 00:00:00 2001 From: ru Date: Fri, 29 Nov 2002 11:39:20 +0000 Subject: mdoc(7) police: scheduled sweep. Approved by: re --- share/man/man4/ata.4 | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) (limited to 'share/man/man4/ata.4') diff --git a/share/man/man4/ata.4 b/share/man/man4/ata.4 index 43de261..912785f 100644 --- a/share/man/man4/ata.4 +++ b/share/man/man4/ata.4 @@ -168,12 +168,13 @@ at a later time when the system is up and running, see .Xr atacontrol 8 . .Pp The driver attempts to set the maximum performance transfer mode on your disk -drives by selecting the highest possible DMA mode. However the +drives by selecting the highest possible DMA mode. +However the .Nm -driver sometimes issue the message -"DMA limited to UDMA33, non-ATA66 cable or device", +driver sometimes issues the message +.Dq Sy "DMA limited to UDMA33, non-ATA66 cable or device" , if the cable is ATA66 (or above) compliant, it is because the other device -on this channel states it can only accept upto UDMA2/ATA33 signals. +on this channel states it can only accept up to UDMA2/ATA33 signals. ATAPI devices are left in PIO mode because DMA problems are common despite the device specifications. You can always try to set DMA mode on an ATAPI device using @@ -184,7 +185,7 @@ support it and can .Em hang the system. .Sh FILES -.Bl -tag -width "/sys/i386/conf/GENERIC " -compact +.Bl -tag -width ".Pa /sys/i386/conf/GENERIC" -compact .It Pa /dev/ad* ATA disk device nodes .It Pa /dev/acd* -- cgit v1.1