From owner-freebsd-scsi Thu Dec 10 09:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21925 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:57:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21913 for ; Thu, 10 Dec 1998 09:57:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA11112; Thu, 10 Dec 1998 10:57:26 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812101757.KAA11112@panzer.plutotech.com> Subject: Re: options FAILSAFE In-Reply-To: from spork at "Dec 10, 98 11:51:13 am" To: spork@super-g.com (spork) Date: Thu, 10 Dec 1998 10:57:26 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork wrote... > I've always wondered exactly what it does... Is it strictly a scsi thing > or does it touch other bits and pieces? LINT says it enables tag queueing > on the ncr. Does anyone know what else it does, and whether it does > anything if you're running CAM? It doesn't do anything to affect the SCSI subsystem if you're running CAM. The best way to find out what it does is: cd /usr/src/sys find . -name "*.[ch]" -print |xargs grep FAILSAFE It appears that it only affects some Cyrix options now. (I could have missed something by only looking at *.c and *.h, though.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message