On Tue, Mar 04, 2003, Guennadi Liakhovetski <[EMAIL PROTECTED]> wrote: > Further to my earlier email, regarding an error on repeated access to a > digital photocamera, I checked UHCI specs, and I found out, that the error > reported by the driver actually corresponds to the "babbling" condition on > the bus. From what I've read, it looks like this error should be more or > less random, also, some drivers suggest that babbling can be related to a > bad cable. None of these holds in my case. Again, exactly what I see - > gphoto2 is called to read the directory listing on the camera with > debugging turned on, first time it succeeds, but the second time it fails > with interrupt status 3, babble bit set, and as gphoto2 tries to read out > the listing, it actually gets it, but ALWAYS before it there are 0x40 > bytes with THE SAME contents every time. So, is it likely to be caused by > a faulty USB-implementation on the camera, or by the incomplete / wrong > support of this camera by gphoto2? Another "strabge" thing - the vendor > and the product IDs of my Concord Eye-Q 4330z match those of Traveler > SX410z camera... What should this mean? I think, I'll try to contact the > manufacturer to find this out:-)
Babbles can also be the result of a protocol error. Specifically, if the driver only requests 6 bytes of data, but the device wants to send 8, that will result in a babble. It kinda sounds like there may be some sort of data toggle problem as well. What UHCI driver are you using? What kernel version? JE ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
