I will repeat what I was told by an engineer here at Microtek. Microtek
scanners use SCSI commands through the 1394 chipset.
I would be suprised to hear that a manufacturer has done something different
than port their already existing technology through the 1394 chipset/port.
I'm a little over my head in this area, but I think Karl is right.
Michael
-----Original Message-----
From: owner-sane-devel@mostang.com
[mailto:owner-sane-devel@mostang.com]On Behalf Of Karl Heinz Kremer
Sent: Sunday, January 28, 2001 8:12 AM
To: sane-devel@mostang.com
Cc: Allan Engelhardt
Subject: Re: FireWire (i.Link / 1394) support?
On Sun, Jan 28, 2001 at 10:00:48AM -0500, Douglas Gilbert wrote:
> Allan Engelhardt wrote:
> >
> > Couldn't find anything in the archives ot the FAQ, so here goes:
> >
> > Has anybody been looking at support for the FireWire (a.k.a. i.Link,
a.k.a. i1394) bus, now that it is supported (-ish) in the 2.4 Linux kernel?
> >
> > There are a copule of neat scanners with this interface that I'd like to
use.
>
> Allan,
> If the scanners use the SBP-2 protocol (i.e. scsi command
> set) over 1394 then there is a driver in beta test written
> by James Goodwin at:
> http://firewire.zawa.com/sbp2/
>
> He mentions that it has been tested on a Epson 1394 scanner.
Not quite correct: First of all it was an EPSON Expression 1600
scanner and James has no first hand experience with this scanner -
I have one here running with the IEEE1394 interface, and it was
me who fixed the SBP-2 driver to allow for the EPSON scanner to
work. EPSON is not doing anything special, so I would guess that
ever other scanner with an IEEE-1394 interface would also work
as long as SANE supports the SCSI version of the scanner.
Karl Heinz
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Wed Feb 07 2001 - 08:53:28 PST