Frederic Peters a écrit :
Aurelien Jarno wrote:
Would you mind going back to 4KB blocks so we can hope for a working
libgphoto2/libusb combination in Sarge ?
I agree to do that in Sarge but not in Sid, as it would decrease the
transfer rate of some devices by about 20%. For Sid the code has to be
fixed in libgphoto2.
Great; and then you can explain me how libusb should be called by
libgphoto2 so I can fix it correctly in sid :)
Actually I don't know exactly what to do. I have looked at to the
backend code and everything seems ok, though I haven't looked very deep.
The user interface of libusb has not changed in the latest versions,
only the way to communicate with the kernel.
If the backend is working with 4 kB blocks but not with 16 kB blocks, it
looks like a buffer problem. For example the problem of the other
backend was that it was trying to read more than 4 kB into a 4 kB buffer.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`- people.debian.org/~aurel32 | www.aurel32.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
