Hi,
Why is usb_clear_halt() called unconditionally when usb_interrupt_read()
returns an error? A possible error can be -ETIMEDOUT for example and in this
case there is no need to call usb_clear_halt(). I've a problem that interrupt
packets get lost from time to time because of usb_clear_halt().
t find a more suitable one,
Thanks in advance,
Matias Eissler
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060524/08d6f2c6/attachment.html
From jsm...@suse.de Wed May 24 10:18:36 2006
From: j
On Tuesday 23 May 2006 20:47, Dietmar Segbert wrote:
> Hello Rene and Jose,
> hello list,
>
> now i have tested the following commands:
>
> scanimage -d avision >test.pnm 2>error.asc
> (door was closed an no film holder)
>
> scanimage -d avision --frame 1 --resolution 2820 >bild.pnm 2>error1.asc
>
On Wednesday 24 May 2006 02:24, Wittawat Yamwong wrote:
> Hi,
>
> Why is usb_clear_halt() called unconditionally when usb_interrupt_read()
> returns an error? A possible error can be -ETIMEDOUT for example and in
> this case there is no need to call usb_clear_halt(). I've a problem that
> interrupt
Hi,
> From your first log we can see that the scanner is recognised. It sees that
> there is no film holder, it waits for the lamp to warm up, all perfect, and
> then it starts the calibration process. Everything seems to be ok, until we
> get to the portion that I am attaching. There we start hav
Hello rene,
hello Jose,
after a lot of testing, i have looked to the right of the usb device,
because i did not find the scanner as user and so i have set the rights of
the scanner /roc/bus/usb/004/003 to root:usb (chown root:usb ...
Voila, the scanner works. I will send the first scanned neg
