Hi,
Frederic Peters a écrit :
Adalbert Dawid wrote:
Package: libgphoto2-2 Version: 2.1.5-5.0 Followup-For: Bug #308290
Indeed, after installing the three debs everything works fine again! (Would be great if this bug could be eliminated before the Sarge release...)
Aurelien, this is another camera that works with MAX_READ_WRITE set at 4KB but not at 16KB. This value really looks hardcoded, I can't find how libgphoto2 could fallback to a working value. Is there a way ?
The USB devices don't see this kind of block size, they only see a block size of 64 or 512 bytes depending if they are USB 1.1 or USB 2.0 devices.
The block size you are talking about is only the block size to dialog with the kernel. So it is not the camera which don't work with this block size, but rather the driver.
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.Would you mind going back to 4KB blocks so we can hope for a working libgphoto2/libusb combination in Sarge ?
Bye, Aurelien
-- .''`. 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]
