Right after making the LIBUSB branch, I realized the problem: sending control messages isn't the problem, opening the proper device is.
IMHO, libusb does an excellent job of abstracting USB devices, but this abstraction makes it difficult for fxload to handle its original job of downloading firmware to a specific device (and not just any device that matches a given VID/PID).
...
I'm going to ponder this one some more, but I'm leaning towards not trying to merge the libusb-enabled version back into the main branch. Suggestions welcome.
Hmm, maybe the problem is with the "libusb" API then ... which would suggest that's where the fix should be. I don't know who's maintaining it lately.
User mode APIs for the host side of Linux are a bit problematic. I understand that MS-Windows has an especially bogus model for discovering devices, but the MacOS X is more reasonable; and that neither offers the relatively full access Linux does.
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
