Date: Tue, 11 Feb 1997 18:35:34 +0100 From: se@freebsd.org (Stefan Esser) To: craig@progroup.com (Craig Shaver) Cc: scsi@freebsd.org Subject: Re: 2940 and ncr target problems re: HELP!! ST32155W - Not detected during probing!! Message-ID: <19970211183534.ZZ52644@x14.mi.uni-koeln.de> In-Reply-To: <32FF4A6C.2781E494@progroup.com>; from Craig Shaver on Feb 10, 1997 08:18:52 -0800 References: <199702072134.NAA29174@vader.cs.berkeley.edu> <199702101012.TAA06339@madoka.hal.t.u-tokyo.ac.jp> <32FF4A6C.2781E494@progroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 10, craig@progroup.com (Craig Shaver) wrote: > I believe this may point out a significant problem with the driver for > the > 2940W and most likely the ncr also. I have tried to use a wide drive on > the ncr825 and 875 at a target id greater than 7. It would not work. I > am not sure of the exact reason, but after seeing the problems Ajith > had, > I believe there is a bug in the drivers. > > I went through the ncr.c source for the 2.1.6 driver and saw in every > instance, that the target id was being masked with the literal '7' which > is '111'b. This only allows a total of 8 targets on the board. The > wide > controllers physically allow up to 16 targets. That would be a mask of > '1111'b, or 15, or 017, or 0x0f. Of course target 7 is usually reserved > for > the target id of the controller hba itself. This has been fixed in the NCR driver in -current and -stable for some time, but the changes had not made it into 2.1.6. Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970211183534.ZZ52644>