Alan, Thanks for the answer. No doubts until now.
I'm analysing the logs, and noticed that the windows driver, after issuing an initial command, it will spend 256*pattern packets cycling from command 0x00 to 0xFF. The pattern consists basically on a sequence of commands, changing only 1 value (the iterator): 4OUT+3IN. I'm being able to reproduce the logs correctly, so far (I'm going at 0x24). Tried to cycle directly to 0xFF without checking for matches at the return values, but no success. Latest values doesn't match, I'll have to check that out manually - more on this later. Anyway, what I really want to know is: is this an expected behaviour? It's weird that the camera has to iterate 256 times through its registers to get to usable state... what might be going on here? And what's the point of issuing 3 consecutive reads in the pattern, when just Index is decremented--? Have anyone found a similar behaviour? -- - Nuno Tavares http://nthq.cjb.net/ ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
