[1979] in linux-scsi channel archive
Re: Latest NCR53C8XX driver update., Suggestion ...
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Wed Jun 11 17:18:15 1997
Date: Wed, 11 Jun 1997 23:02:24 +0200 (MET DST)
From: Gerard Roudier <groudier@club-internet.fr>
To: "Mr. James W. Laferriere Network Engineer" <babydr@nwrain.net>
cc: Linux Scsi maillist <linux-scsi@vger.rutgers.edu>
In-Reply-To: <Pine.LNX.3.95q.970610213751.3677F-100000@filesrv1.baby-dragons.com>
On Tue, 10 Jun 1997, Mr. James W. Laferriere Network Engineer wrote:
> I am quite happily running the '1.18i' driver, although I
> couldn't help but notice that to get from '1.18i' to 2.3
> I would have to go down to 1.18c (Last full distro was 1.18c)
> then go up the chain from there. Plus Slackware & varesearch
> are using the 1.18i driver . (3.2) , (sent to list)
Stabilization of driver version 1.18 was necessary in order to safely add
severall interesting enhancements to the driver.
Using driver version 2.3 is possible by patching a fresh 2.0.X (X>=27)
kernel tree. It is exactly what I do each time on a 2.0.29 tree, prior to
making a new patch available in order to check that all is ok.
(See ftp://linux.wauug.org/pub/roudier/README).
Here are the corresponding instructions extracted from the README.
--------------------------------------------------------------------------
If you enjoy with experimental software, you can try driver version 2.3
under linux-2.0.29 or 2.0.30. Patches are the following:
ncr53c8xx-1.12d-to-1.18d-for-linux-2.0.29.patch.gz
Development/ncr53c8xx-1.18d-to-2.0.patch.gz
Development/ncr53c8xx-2.0-to-2.0a.patch.gz
Development/ncr53c8xx-2.0a-to-2.1.patch.gz
Development/ncr53c8xx-2.1-to-2.1a.patch.gz
Development/ncr53c8xx-2.1a-to-2.2b-for-linux-2.0.29.patch.gz
Development/ncr53c8xx-2.2b-to-2.2c.patch.gz
Development/ncr53c8xx-2.2c-to-2.3.patch.gz
People who absolutely want to use the driver under linux-2.0.27 can apply first
the patch 'ncr53c8xx-12c-to-12d-for-2.0.27.patch.gz' and then the above ones.
Let me know if this driver version works under 2.0.27 since I did'nt try it.
NvRAMs of Symbios compatible and Tekram DC-390/U/F/W boards are supported.
-----------------------------------------------------------------------------
Despite all heavy changes, driver 2.# series has been very reliable.
We have been very fortunate in my opinion since a small bug in a low
level driver may have very catastrophic effects.
> A patch set (occasionally) from the last 1.18# series to the
> latest developement series sure would be nice.
That will not solve the problem, since 1.18i is perhaps not the last
1.18# serie.
Even using CVS will not solve the problem, since changes are often done
at the same source location, and, as you know, some other linux kernel
files are related to drivers (Config.in, Configure.help, ...) and
so, patches may depend on linux tree version too.
A comfortable solution would be that a real 2.0.X stable linux be
released.
In any case, my experience and feeling is that version 2.3 is as reliable
as version 1.18i. So, in my opinion, people who will switch to 2.3 will
probably stick with, especially if they use recent 875 boards with NvRAM.
Linux-2.0.31 will be released with driver version 1.18i.
A patch against driver version 1.18i will be needed only when linux-2.0.31
will be made available.
Gerard.
PS: if a patch against 2.0.29/30 + ncr53c8xx-1.18i can really help, I
will make it available. People who want such a patch can mail me
directly.
