Date: Fri, 14 Jun 2002 17:50:02 -0700 (PDT) From: David Malone <dwmalone@maths.tcd.ie> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/39202: ata(4) refer to sysctl(8) instead of atacontrol(8). Message-ID: <200206150050.g5F0o2J99310@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/39202; it has been noted by GNATS. From: David Malone <dwmalone@maths.tcd.ie> To: Cyrille Lefevre <cyrille.lefevre@laposte.net> Cc: FreeBSD-gnats-submit@FreeBSD.org, sos@FreeBSD.org Subject: Re: misc/39202: ata(4) refer to sysctl(8) instead of atacontrol(8). Date: Sat, 15 Jun 2002 01:47:55 +0100 On Wed, Jun 12, 2002 at 10:29:59PM +0200, Cyrille Lefevre wrote: > while it should refer to atacontrol(8) to change ata modes > since the sysctl hw.atamodes doesn't exists anymore. I think the ata(4) man page has missed a few MFCs. The following diff would sync it with -current (leaving out the bits which relate to -current only device stuff). Soren - would you like me to commit this when the code freeze is over, or would you like to do it on your next MFC? David. --- src/share/man/man4/ata.4:1.3.2.14 Sun Feb 10 07:24:08 2002 +++ src/share/man/man4/ata.4 Fri Nov 2 12:22:17 2001 @@ -72,11 +74,11 @@ .It Va hw.ata.atapi_dma set to 1 for DMA access, 0 for PIO (default is PIO). .It Va hw.ata.wc -set to 1 to enable Write Caching, 0 to disable (default is enabled) -(WARNING might cause data loss on power failures) +set to 1 to enable Write Caching, 0 to disable (default is disabled). +(WARNING: might cause data loss on power failures.) .It Va hw.ata.tags -set to 1 to enable Tagged Queuing support, 0 to disable (default is disabled) -(only IBM DPTA and DTLA drives support that) +set to 1 to enable Tagged Queuing support, 0 to disable (default is disabled). +(Only IBM DPTA and DTLA drives support that.) .El .Sh DESCRIPTION This driver provides access to disk drives, ATAPI CD-ROM and DVD drives, @@ -86,9 +88,9 @@ .Pp The currently supported controllers with their maximum speed include: .Pp -.Bl -tag -width "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -compact +.Bl -tag -width "Promise Ultra/Fasttrak-100 TX2/TX4" -compact .It Acerlabs Aladdin -Ultra DMA 33 (UDMA2), 33 MB/sec +Ultra DMA 100 (UDMA5), 100 MB/sec (depending on model, max stated at boot) .It AMD 756 Ultra DMA 66 (UDMA4), 66 MB/sec .It AMD 766 @@ -101,10 +103,14 @@ Ultra DMA 100 (UDMA5), 100 MB/sec .It Cypress 82C693 DMA 2 (WDMA2), 16 MB/sec +.It Cyrix 5530 +Ultra DMA 33 (UDMA2), 33 MB/sec .It HighPoint HPT366 Ultra DMA 66 (UDMA4), 66 MB/sec .It HighPoint HPT370 Ultra DMA 100 (UDMA5), 100 MB/sec +.It HighPoint HPT372 +Ultra DMA 133 (UDMA6), 133 MB/sec .It Intel PIIX DMA 2 (WDMA2), 16 MB/sec .It Intel PIIX3 @@ -125,57 +131,41 @@ Ultra DMA 66 (UDMA4), 66 MB/sec .It Promise Ultra/Fasttrak-100 Ultra DMA 100 (UDMA5), 100 MB/sec +.It Promise Ultra/Fasttrak-100 TX2/TX4 +Ultra DMA 100 (UDMA5), 100 MB/sec .It ServerWorks ROSB4 Ultra DMA 33 (UDMA2), 33 MB/sec .It SiS 5591 Ultra DMA 33 (UDMA2), 33 MB/sec -.It Cyrix 5530 -Ultra DMA 33 (UDMA2), 33 MB/sec .It VIA 82C586 Ultra DMA 33 (UDMA2), 33 MB/sec +.It VIA 82C596 +Ultra DMA 66 (UDMA4), 66 MB/sec (depending on model, max stated at boot) .It VIA 82C686a Ultra DMA 66 (UDMA4), 66 MB/sec .It VIA 82C686b Ultra DMA 100 (UDMA5), 100 MB/sec .El .Pp -All unknown chipsets can be supported at the maximum speed of 16 MB/sec. +All unknown chipsets are supported at the maximum speed of 16 MB/sec. .Pp The .Nm driver also allows for changes to the transfer mode of the devices -at a later time when the system is up and running. +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. 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 the sysctl -method described here, +You can always try to set DMA mode on an ATAPI device using +.Xr atacontrol 8 , but be aware that your hardware might .Em not support it and can .Em hang the system. -.Pp -To see the devices' current access modes, use the command line: -.Pp -.Dl sysctl hw.atamodes -.Pp -which results in the modes of the devices being displayed as a string -like this: -.Pp -.Dl hw.atamodes: dma,pio,---,pio,dma,---,dma,---, (--- = no device) -.Pp -This means that ata0-master is in DMA mode, -ata0-slave is in PIO mode, -and so forth. -You can set the mode with sysctl and a string like the above, -for example: -.Pp -.Dl sysctl hw.atamodes=pio,pio,---,dma,pio,---,dma,---, -.Pp -The new modes are set as soon as the sysctl command returns. .Sh FILES .Bl -tag -width "/sys/i386/conf/GENERIC " -compact .It Pa /dev/ad* @@ -219,6 +209,9 @@ unless they are run at the non-UDMA4 device's lower speed. The driver has been designed to handle that kind of setup but lots of older devices do not like this. +.Sh SEE ALSO +.Xr atacontrol 8 , +.Xr burncd 8 .Sh HISTORY The .Nm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206150050.g5F0o2J99310>