From owner-freebsd-current  Mon Dec 16 16:18:27 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id QAA18185
          for current-outgoing; Mon, 16 Dec 1996 16:18:27 -0800 (PST)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA18138;
          Mon, 16 Dec 1996 16:17:54 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr2-41.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA02496
  (5.67b/IDA-1.5); Tue, 17 Dec 1996 01:17:18 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.4/8.6.9) id BAA02886; Tue, 17 Dec 1996 01:17:15 +0100 (CET)
Message-Id: <Mutt.19961217011715.se@x14.mi.uni-koeln.de>
Date: Tue, 17 Dec 1996 01:17:15 +0100
From: se@FreeBSD.org (Stefan Esser)
To: bde@zeta.org.au (Bruce Evans)
Cc: max@wide.ad.jp, se@FreeBSD.org, current@FreeBSD.org
Subject: Re: Error with current ncr.c
References: <199612161639.DAA16927@godzilla.zeta.org.au>
X-Mailer: Mutt 0.53
Mime-Version: 1.0
In-Reply-To: <199612161639.DAA16927@godzilla.zeta.org.au>; from Bruce Evans on Dec 17, 1996 03:39:29 +1100
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

On Dec 17, bde@zeta.org.au (Bruce Evans) wrote:
> >I'll make sure that the #include is 
> >ignored in the ncrcontrol build ...
> 
> This doesn't work, since e.g. SCI_NCR_DFLT_TAGS affects MAX_START which
> affects `struct ncb' which must be the same in the kernel and ncrcontrol.
> This is the old FAILSAFE configuration bug.

Yes, I know about this.

The best way to have a kernel and corresponding ncrcontrol
with non-default settings of those defines is to put them
at the start of /sys/pci/ncr.c, where both the driver and 
the ncrcontrol build will see them. 

This is in part a result of the fact, that "ncrcontrol" 
was mainly an internal test tool, which got features over
time, some of which seemed nice to be generally available.

I've planned other major changes to the driver, and won't
spend time, now, to clean this up. My spare time is rather
limited (whose isn't), and I think I should work on other
things right now (eg. full Ultra-SCSI support and other 
driver improvements).

Regards, STefan