summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorroam <roam@FreeBSD.org>2004-12-21 20:02:50 +0000
committerroam <roam@FreeBSD.org>2004-12-21 20:02:50 +0000
commit5a6d53a6697ca04b164b12374e83e6e895dd0fab (patch)
tree9aea1f57c038dbd01458dc431e264d60253100e5 /share
parent968f03faa7b3b44011e8bcc285dd7cf40ab5e13b (diff)
downloadFreeBSD-src-5a6d53a6697ca04b164b12374e83e6e895dd0fab.zip
FreeBSD-src-5a6d53a6697ca04b164b12374e83e6e895dd0fab.tar.gz
And this, kids, is what happens if you act on a patch without looking
at the mailing list to see if there isn't any more discussion just around the corner. Here's the update to the other part of the manpage that deals with the hw.ata.atapi_dma loader tunable and initializing ATAPI devices in PIO or DMA mode. PR: 75021 Submitted by: Craig Rodrigues <rodrigc@crodrigues.org> Spotted by: Joel Dahl <joel@automatvapen.se>
Diffstat (limited to 'share')
-rw-r--r--share/man/man4/ata.45
1 files changed, 4 insertions, 1 deletions
diff --git a/share/man/man4/ata.4 b/share/man/man4/ata.4
index 90541da..847b522 100644
--- a/share/man/man4/ata.4
+++ b/share/man/man4/ata.4
@@ -161,7 +161,10 @@ or could not be detected properly,
or that one of the devices on the channel only accepts up
to UDMA2/ATA33.
.Pp
-ATAPI devices are set to PIO mode by default because severe DMA problems are
+Unknown ATAPI devices are initialized to DMA mode if the
+.Va hw.ata.atapi_dma
+tunable is set to 1 and they support at least UDMA33 transfers.
+Otherwise they are set to PIO mode because severe DMA problems are
common even if the device capabilities indicate support.
You can always try to set DMA mode on an ATAPI device using
.Xr atacontrol 8 ,
OpenPOWER on IntegriCloud