But back in 2.0.30 I also needed to patch the ncr53c8xx.c driver to make
sure that it wouldn't time out in the middle of a long scan. (I have a
Mustek IISP type which doesn't disconnect.) The sane-scsi man page still
says:
...find the line "if (np->latetime>10)"
in file ncr53c8xx.c (normally in directory
/usr/src/linux/drivers/scsi) and change the
constant 10 to, say, 60 (one minute).
However, the ncr53c8xx.c file changed somewhere between 2.0.30 and
2.0.32. It now handles timeouts a bit differently...
/*----------------------------------------------------
**
** handle ncr chip timeouts
**
** Assumption:
** We have a chance to arbitrate for the
** SCSI bus at least every 10 seconds.
**
**----------------------------------------------------
*/
t = (thistime - np->heartbeat) / HZ;
if (t<2) np->latetime=0; else np->latetime++;
It's not clear (to me, anyway) how to change this updated driver to
allow longer timeouts. Has anyone else run into this problem yet? Does
someone know how to patch this, or should I query the driver maintainer
directly?
Sincerely,
Ray Ingles (248) 377-7735 ray.ingles@fanucrobotics.com
Anagrams of "FANUC Robotics North America":
bun of characteristic maroon omaha reconstruction fabric
a cubic transformation chore cherub fractionation macros
cube of anachronistic mortar
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com