Perhaps for 2.5 we should avoid the swap in the core and fix the drivers.
That's the question ... although it may also be OK to just live with that one API wart, since I think only the device descriptor has that (documented?) issue.
We'd need a good tester with a big-endian machine to make sure the enumeration and driver binding code didn't break though. "Less work" may be better.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
