[4930] in linux-scsi channel archive
Re: ncr53c8xx 3.0 & scanner
daemon@ATHENA.MIT.EDU (Gerard Roudier)
Sat Oct 17 09:09:07 1998
Date: Fri, 16 Oct 1998 22:27:28 +0200 (MET DST)
From: Gerard Roudier <groudier@club-internet.fr>
To: Peter Daum <gator@cs.tu-berlin.de>
cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.4.02A.9810161044520.381-100000@swamp.bayern.net>
On Fri, 16 Oct 1998, Peter Daum wrote:
> On Thu, 15 Oct 1998, Gerard Roudier wrote:
> [...]
> > Using tags with a scanner is very optimistic. ;-)
> > The driver normally catches this feature from the INQUIRY response.
> > Could you send me the INQUIRY response sent by the scanner?
> > You can get it using scsiinfo or scsi-config tool.
>
> scsiinfo doesn't produce any useful information; obviously
Just enter: scsiinfo -i /dev/sge
You should get an output like the following: (I got it from a hard drive)
Inquiry command
---------------
Relative Address 0
Wide bus 32 0
Wide bus 16 1
Synchronous neg. 1
Linked Commands 1
Command Queueing 1
SftRe 0
Device Type 0
Peripheral Qualifier 0
Removable? 0
Device Type Modifier 0
ISO Version 0
ECMA Version 0
ANSI Version 2
AENC 0
TrmIOP 0
Response Data Format 2
Vendor: SEAGATE
Product: ST39102LW
Revision level: 0004LJ097683
------------
> opening the scsi generic devices is not allowed, no matter how
> the file permissions are set:
> open("/dev/sge", O_RDONLY) = -1 EACCES (Permission denied)
>
> However, from a DOS based Adaptec SCSI Explorer I know, that the
> Scanner claims to be SCSI-2 compliant but does not pretend to
> support any other "special features" like tagged command queueing
> or sync transfers.
I donnot expect a scanner to support command queueing. 'Sync' could be
possible for a scanner.
> > Do you get the exact same error messages as above when the error occurs
> > and tags are disabled?
>
> With tags disabled, there isn't any real error message anymore;
> when I try to do open the scanner a second time, xscanimage just
> gets stuck in its inquiry routine and the driver reports a
> timeout every 10 minutes:
The INQUIRY commande/response seems to trigger the problem, so let me know
what 'scsiinfo -i' prints out for your scanner.
> I also tried the other NCR driver (53c7,8xx) but couldn't even
> load it, because it obviously doesn't believe in interrupt
> sharing and the NCR810 card and the onboard Adaptec controller
> both use IRQ 9.
This one will not use tags (command queuing) because it does not support
this feature.
Regards,
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
