On 11 Aug 2012 02:53 , Pete Batard wrote: > > Note however that there's going to be a change of plan with regards to > FX2/FX3 support, as I have just completed the porting of fxload [1] from > linux-hotplug [2] to libusbx, with the aim of including it as a sample. > As a matter of fact, it is now included as a full fledged sample in the > 0K branch [3]. > > For now support is only for FX2 and earlier, so we need to re-apply an > FX3 patch. I'll try to take care of that, but Markus, if you feel like > you want to go for it, don't hesitate.
That sounds like the optimum solution. I've been reluctant to come up with this in the first place due to lack of time (as I have to keep my focus on developing firmware for the FX3). I doubt I won't be able to go for it in the foreseeable future, as long as the simple approach works. One thing that might changes necessary however is the new firmware format that Cypress talks about in its FX3 API 1.2 release notes: http://www.cypress.com/?docID=38763 With prior versions, the FX3 had to be reset by an on-board switch or un-/replugging the power supply. Now the firmware should allow a reset while the device is connected (p. 6 of the manual). Still, right now it's still unclear how such a reset is going to be initiated. I'll keep you updated. All the best, /Markus ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
