[6095] in linux-scsi channel archive
ncr-8xx-896 driver bundle for 2.0.36
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Sun Mar 14 11:35:44 1999
Date: Sun, 14 Mar 1999 17:31:52 +0100 (MET)
From: Gerard Roudier <groudier@club-internet.fr>
To: linux-scsi@vger.rutgers.edu, ncr53c810@colorado.edu
Hi,
I have made available a patch against 2.0.36 that contains both,
- ncr53c8xx driver version 3.2
- sym53c8xx driver version 1.3a
ftp://ftp.tux.org/pub/roudier/misc-stuff/ncr-8xx-896-bundle-for-linux-2.0.36.patch.gz
The equivalent patch against linux-2.2.3 (minus a minor change in sym53c8xx
driver) had been made available a couple of days ago:
ftp://ftp.tux.org/pub/roudier/misc-stuff/ncr-8xx-896-bundle-for-linux-2.2.3.patch.gz
With these patches, you can configure the drivers as you want, i.e:
a) both linked to the kernel
b) one linked to the kernel, the other one as module
c) both as module
d) none :-)
Except on systems that use both early chips (810 rev < 16, 825 rev < 16
and 815) and recent ones, you may not want to use the both drivers at the
same time on your system. But you may want to play using them alternatively
at will or just using both at the same time for fun. ;-)
For the moment, I have not decided yet how I will organize patches at the
tux site. Will probably look like the following:
- One initial patch for 2.0.36 (the current one is quite fine)
- One initial patch for 2.0.37 (will come)
- One directory for ncr53c8xx driver diffs
- One directory for sym53c8xx driver diffs
- One patch for every 2.2.X kernel until the bundle will be included
into the kernel main-stream.
I will try to have this stuff done for the next week-end.
Regards,
Gérard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
