On Mon, 2005-04-04 at 14:06 -0700, David Brownell wrote: > That's exactly as I described. 64 bytes in one packet, 17 in the next. > > You are NOT getting 81 bytes in one frame/packet!!
Ok, thanks for clarifying. > > I suppose if I told the kernel I want 40 bytes it'd give me 40, then 40 > > and then 1, after which the cycle would restart. > > No, it should give you 40 bytes with an -EOVERFLOW error since the > device sent 64 bytes in that packet. Then probably 17 in the next. Hm, ok. But the device announces wMaxPacketSize = 32. Whatever. > If the two reports always go together, and there are no cases where > you'd be getting a 64 byte (maxpacket sized) report followed by nothing > for many frames ... yes. I think they do, I haven't seen any other behaviour yet. I guess is this is what I'll stay with then. Thanks, johannes
signature.asc
Description: This is a digitally signed message part
