The CMD640 workaround is now enabled by default.

This commit is contained in:
Wolfgang Helbig 1997-08-30 10:24:30 +00:00
parent 65dc252567
commit c52150a830
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=1899

View file

@ -1,12 +1,12 @@
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
<!-- $Id: FAQ.sgml,v 1.64 1997-08-11 02:07:58 steve Exp $ -->
<!-- $Id: FAQ.sgml,v 1.65 1997-08-30 10:24:30 helbig Exp $ -->
<article>
<title>Frequently Asked Questions for FreeBSD 2.X
<author>Maintainer: Peter da Silva <tt><htmlurl url='mailto:pds@FreeBSD.ORG'
name='&lt;pds@FreeBSD.ORG&gt;'></tt>
<date>$Date: 1997-08-11 02:07:58 $</date>
<date>$Date: 1997-08-30 10:24:30 $</date>
<abstract>
This is the FAQ for FreeBSD systems version 2.X All entries are
@ -1625,25 +1625,9 @@ quit
<p>It's broken. It cannot handle commands on both channels
simultaneously.
<p>There's a workaround available now, but as of FreeBSD 2.2,
we felt it was still not long enough in the source tree to
shake out any potential bugs. Hence it is disabled by default.
To enable it, you have to reconfigure and recompile your kernel
with
<verb>
options "CMD640"
</verb>
in the config file.
<p>In order to install the system, you must however ensure
that only one channel of this controller will be used. Don't
forget about ATAPI CD-ROM drives here -- if you are using one,
it must be the slave on the primary channel. Once your new
kernel is in place, you can rearrange the machine as you like.
<p>The workaround is likely to be enabled by default in future
versions.
<p>There's a workaround available now and it is enabled automatically
if your system uses this chip. For the details refer to the
manual page of the disk driver (man 4 wd).
<sect>
<heading>Commercial Applications</heading>