I'm trying to get mii support working properly with the ax8817x driver but I'm hitting a big stumbling block. I have the following functions that handle the reads but I always get a return code of 2 from the second ax_read_cmd (the one that actually pulls the value, calls ax_control_msg, etc.). In tracing through ax_read_cmd, that return code is what is passed back from usb_submit_urb (offending code in ax8817x found below). In following usb_submit_urb, I didn't see any cases where it would return 2, but many places with EINVAL, etc which are 22 or 19, etc.
Any thoughts?
Very interesting development. On a hunch, I went ahead and cast the indx call to ax_read_cmd to __u16 and it looks like I'm getting the right stuff back from mii! I still get the result value of 2 which I thought may be a 'bytes read' type of thing, but it appears that usb_submit_urb will return 0 on success. Very odd.
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
