Hello all!

I wanted to post the solution for my problem with SANE and the Epson
Perfection 4180 Color, should it prove useful for someone else in the
future.  As previously mentioned, the epkowa drivers and related plugin were
loaded per the Avasys instructions.  The logs were showing evidence that the
firmware file was not being loaded (all calls to the device were failing).
In an earlier attempt to remove ambiguity while debugging the SANE config
files (before properly loading epkowa), I had added the vendor and product
IDs to the usb line in the conf file (usb 0x04b8 0x0118), thereby triggering
a bug in the backend.  According to Olaf Meeuwissen, who was a great help in
all of this, the problem only affects models that require iscan plugins and
this bug has been fixed for the next release.  Thanks again, Olaf!

-Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060717/b674206b/attachment.html
From [email protected]  Mon Jul 17 13:03:48 2006
From: [email protected] ([email protected])
Date: Mon Jul 17 13:04:04 2006
Subject: [sane-devel] HELP! Epson Perfection 4180 Photo
In-Reply-To: <[email protected]>
References: <[email protected]>
        <[email protected]>
        <[email protected]>
        <[email protected]>
        <[email protected]>
Message-ID: <[email protected]>

Right, silly me...if it wasn't obvious in my message below, using usb
without the vendor and product IDs worked fine.  I can now acquire very nice
images into GIMP using Xsane, iScan, Xscanimage, etc.

-Brandon


On 7/17/06, [email protected] <[email protected]> wrote:
>
>  Hello all!
>
> I wanted to post the solution for my problem with SANE and the Epson
> Perfection 4180 Color, should it prove useful for someone else in the
> future.  As previously mentioned, the epkowa drivers and related plugin were
> loaded per the Avasys instructions.  The logs were showing evidence that the
> firmware file was not being loaded (all calls to the device were failing).
> In an earlier attempt to remove ambiguity while debugging the SANE config
> files (before properly loading epkowa), I had added the vendor and product
> IDs to the usb line in the conf file (usb 0x04b8 0x0118), thereby triggering
> a bug in the backend.  According to Olaf Meeuwissen, who was a great help in
> all of this, the problem only affects models that require iscan plugins and
> this bug has been fixed for the next release.  Thanks again, Olaf!
>
> -Brandon
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060717/fa2c4929/attachment.htm
From [email protected]  Mon Jul 17 20:15:12 2006
From: [email protected] (Tabor Kelly)
Date: Mon Jul 17 20:16:22 2006
Subject: [sane-devel] USB-sniff help with Canon FS2720U
Message-ID: <[email protected]>

Hello,

I am hoping to write a SANE backend for my Canon FS2720U slide
scanner. After playing with Snoopy Pro and deciding that it was
lacking in many regards, I have switched so USB-sniff. However, I am
new to USB and device drivers in general and I am looking for some
help reading the USB-sniff output.

Specifically, I want to know how the elements of the USB-sniff output
map to the USB 1.1 specification. Here is the first log I attempted to
read (http://tabor.taborandtashell.net/sane-fs2720u/turned_on.LOG).
This is just what I get when I turn on the scanner for the first time.
So, I have a long list of questions and I have searched for answers
but I couldn't find any.

What does Status in USB-sniff map to in the USB 1.1 spec?

Does URB_FUNCTION_CONTROL_TRANSFER refer the the Control Transfer
discussed in the USB 1.1 spec? If so, what is a
URB_FUNCTION_CLASS_INTERFACE? I couldn't find it in the spec.

What are the TransferFlags and why can't I find their description in
the USB 1.1 spec?

TransferBuffer is just the memory address of the start of the buffer,
right?

What is TransferMDL?

What is UrbLink?

Do RequestTypeReservedBits, Request, Value, and Index in USB-sniff map
to bmRequest, bRequest, wValue, and wLength respectively in the USB
1.1 spec?

Thank You,

Tabor Kelly

Reply via email to