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 Message-ID: <Mutt.19961217011715.se@x14.mi.uni-koeln.de> In-Reply-To: <199612161639.DAA16927@godzilla.zeta.org.au>; from Bruce Evans on Dec 17, 1996 03:39:29 %2B1100 References: <199612161639.DAA16927@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19961217011715.se>