public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Pritchard <steve@silug.org>
To: "Steven P. Cole" <elenstev@mesatop.com>,
	"Eric S. Raymond" <esr@thyrsus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Configure.help entry fix
Date: Thu, 27 Dec 2001 23:42:34 -0600	[thread overview]
Message-ID: <20011227234234.A353@osiris.silug.org> (raw)

Then entry in Configure.help for CONFIG_BLK_DEV_3W_XXXX_RAID starts
out "3ware is the only hardware ATA-Raid product in Linux to date."
This is a mistake, since the driver for the Adaptec 2400A card
(dpt_i2o) is in the kernel.

I've included a patch below to fix that, plus add a note about a data
corruption issue that users should be aware of.  I suppose the entry
should probably also include the standard "If you want to compile this
driver as a module..." block also...

On a side note, shouldn't CONFIG_BLK_DEV_3W_XXXX_RAID really be
something like CONFIG_SCSI_3W_XXXX_RAID?

Steve
-- 
steve@silug.org           | Southern Illinois Linux Users Group
(618)398-7360             | See web site for meeting details.
Steven Pritchard          | http://www.silug.org/

--- Documentation/Configure.help.orig	Fri Dec 21 11:41:53 2001
+++ Documentation/Configure.help	Thu Dec 27 23:34:49 2001
@@ -917,9 +917,13 @@
 
 3ware Hardware ATA-RAID support
 CONFIG_BLK_DEV_3W_XXXX_RAID
-  3ware is the only hardware ATA-Raid product in Linux to date.
-  This card is 2,4, or 8 channel master mode support only.
-  SCSI support required!!!
+  This driver supports the 3ware Escalade 5000, 6000, and 7000-series
+  IDE RAID controllers.
+
+  Note that RAID 5 on 6000-series controllers requires a recent
+  firmware revision.  Running old firmware or old versions of the
+  driver on a degraded RAID 5 array can cause data corruption on the
+  array.  See 3ware's web site for firmware updates.
 
   <http://www.3ware.com/>
 

                 reply	other threads:[~2001-12-28  5:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011227234234.A353@osiris.silug.org \
    --to=steve@silug.org \
    --cc=elenstev@mesatop.com \
    --cc=esr@thyrsus.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox