Hi,
On Fri, Mar 05, 2004 at 12:31:17AM +0100, Oliver Schwartz wrote:
> I have to admit this is a bit above my head. How do I know how many
> urbs are sent / received if I do a bulk transfer? It seems you're
> using an estimate in mustek_usb, but how do you know how many bytes
> you're transferr
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> With libusb? I don't think so. But counting packets works fine.
> I've implemented it in the mustek_usb backend now and (at least for
> me) there are no more timeouts.
I have to admit this is a bit above my head. How do I know how many=20
urb
Hello to all,
> > is there any way for a backend to tell what the current status of the
> > toggle is, before closing the connection?
>
> With libusb? I don't think so. But counting packets works fine. I've
> implemented it in the mustek_usb backend now and (at least for me)
> there are no more
Hi,
On Mon, Mar 01, 2004 at 12:44:26PM -0500, m. allan noah wrote:
> reset is the past tense of reset, since you asked. (dont ask, its
> english).
I was actually asking if it was the endpoint reset that triggered the
bug. But I think that was correct. Concerning the spelling: thanks,
also fixed
Hi,
On Mon, Mar 01, 2004 at 11:46:58AM -0500, m. allan noah wrote:
> if that works, then perhaps there is a libusb/linux kernel error that
> prevents the DATA0/1 toggle from frobbing.
IIRC that's a bug in some USB chipsets. It happens when the connection
is resetted (?). The USB spec says that i
Hi Oliver,
maybe you can use this dump here:
The FIRST call of scanimage -L:
alpha:/var/cache/apt/archives# SANE_DEBUG_SANEI_USB=255 scanimage -L
[sanei_debug] Setting debug level of sanei_usb to 255.
[sanei_usb] sanei_usb_init: couldn't open /dev/usb/scanner0: No such
device
[sanei_usb] san
reset is the past tense of reset, since you asked. (dont ask, its
english).
is there any way for a backend to tell what the current status of the
toggle is, before closing the connection?
allan
On Mon, 1 Mar 2004, Henning Meier-Geinitz wrote:
> Hi,
>
> On Mon, Mar 01, 2004 at 11:46:58AM -050
oliver, not sure if it helps you, but the fujitsu backend does this same
thing on second scans if the first scan used an odd number of usb packets
and then the backend exits. as a simple test, you could add a global
packet counter, and throw an additional pointless request onto the end,
before
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> >>FYI, my Snapscan 1212U_2 works fine with:
> >>- kernel 2.6.3
> >>- backend version 1.0.13
> >>- libusb-0.1.8 (0.1.7 worked as well)
> >
> > Mh, my backend's version is 1.4.35. Maybe something "special"
> > happened in between ...
>
> I haven
D. Winkler wrote:
> Am So, den 29.02.2004 schrieb Klaus-Peter Schrage um 17:52:
>
>
>>FYI, my Snapscan 1212U_2 works fine with:
>>- kernel 2.6.3
>>- backend version 1.0.13
>>- libusb-0.1.8 (0.1.7 worked as well)
>
>
> Mh, my backend's version is 1.4.35. Maybe something "special" happened
> in b
Am So, den 29.02.2004 schrieb Klaus-Peter Schrage um 17:52:
> FYI, my Snapscan 1212U_2 works fine with:
> - kernel 2.6.3
> - backend version 1.0.13
> - libusb-0.1.8 (0.1.7 worked as well)
Mh, my backend's version is 1.4.35. Maybe something "special" happened
in between ...
JFYI
Daniel
Julien BLACHE wrote:
> Oliver Schwartz wrote:
>
>
>>There seems to be a general problem with libusb, sane, and kernel 2.6.
>>I've got another report from a Snapscan 1212 user with similar
>>problems. A user of the epson backend also reported problems.
>
>
> Lots of people upgrading to the 2.
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> I tend to think the problem is limited to the snapscan backend, as
> I've seen quite a number of people on IRC using other backends with
> libusb and either a 2.4 or 2.6 kernel without problem. Might a
> general libusb problem too, that wouldn
Oliver Schwartz wrote:
> There seems to be a general problem with libusb, sane, and kernel 2.6.
> I've got another report from a Snapscan 1212 user with similar
> problems. A user of the epson backend also reported problems.
Lots of people upgrading to the 2.6.3 kernel are switching to libusb
=2DBEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> With my older Kernel 2.4.x and scanner.o everything went fine.
> After switching to 2.6.3, xsane and Co. arent able to use the
> scanner via libusb.
There seems to be a general problem with libusb, sane, and kernel 2.6.=20
I've got another re
> There seems to be a general problem with libusb, sane, and kernel
> 2.6.
> I've got another report from a Snapscan 1212 user with similar
> problems. A user of the epson backend also reported problems.
I'm the one with the Epson 636U. The libusb problem exists with 2.4.25
as well as 2.6.x, at
On Feb 29, 2004, at 6:47 AM, Julien BLACHE wrote:
[ ... ]
> I tend to think the problem is limited to the snapscan backend, as
> I've seen quite a number of people on IRC using other backends with
> libusb and either a 2.4 or 2.6 kernel without problem. Might a general
> libusb problem too, that wo
Hello together,
my current system:
Debian unstable (with the corresponding sane packages)
Kernel 2.6.3
Agfa SnapScan 1236U
With my older Kernel 2.4.x and scanner.o everything went fine. After
switching to 2.6.3, xsane and Co. arent able to use the scanner via
libusb.
Some effects:
sane-find-scan
18 matches
Mail list logo
