On Fri, 21 May 2004, nardelli wrote:
The api for usb_control_msg says, 'If successful, it returns 0, othwise a negative error number', and I didn't see any other way to figure out how much data was being returned.
In the current kernel sources, the kerneldoc for usb_control_msg() says
"If successful, it returns the number of bytes transferred, otherwise a negative error number."
Sorry, I was looking at dated api docs at kernelnewbies.org. I'll use the size returned from usb_control_msg() instead of memset().
-- Joe Nardelli [EMAIL PROTECTED]
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel