On Thu, Sep 23, 2010 at 03:01:32PM +0100, Toby Gray wrote: > I've seen the reply on the libusb list saying that it's perfectly valid > for a bulk read to return 0, thanks for checking that. I'll have a > further look into the problem, but I think I might have to ask on the > libusb list about how to determine when a port has been reset. > > I would hope that there is some way to, as it seems that when Barry next > tries to use the USB interface after the zero read that the generic USB > kernel driver complains about trying to use an interface without having > claimed it.
I saw your messages on libusb as well. This is useful information. In reading your responses, I'm thinking that all we really need to know is whether a 0 size packet is valid for the *Blackberry*. And to my knowledge, there is never such a packet in its communication. In this case, I like the idea of a totally separate exception, with some logging, so that if it ever does encounter a 0 size packet, it will be obvious, recoverable, but also debuggable. :-) If this behaviour is easily configurable too, that would be even better, so that if something goes amiss, we can ask users to test both easily in the field. Does that make sense to you? Thanks again for your detailed work on this, - Chris ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
