From owner-freebsd-scsi  Thu Dec 10 09:42:39 1998
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA19501
          for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:42:39 -0800 (PST)
          (envelope-from owner-freebsd-scsi@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19495
          for <freebsd-scsi@FreeBSD.ORG>; Thu, 10 Dec 1998 09:42:35 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA20595;
	Fri, 11 Dec 1998 04:42:26 +1100
Date: Fri, 11 Dec 1998 04:42:26 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199812101742.EAA20595@godzilla.zeta.org.au>
To: freebsd-scsi@FreeBSD.ORG, spork@super-g.com
Subject: Re: options FAILSAFE
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>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 rots.  In -current, it has no effect except to disable one obscure
initialization of Cyrix CPUs.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message