> While I have to say your code is A LOT cleaner than the fxload one That's because I'm not very smart - breaking problems down is the only hope I have of solving them!
> (and at the very least, I'd like to use your firmware with the vendor > commands for eeprom flashing), If you want to adopt that firmware code, I'm fine with you changing the license to LGPLv2.1 to match your code, provided you keep the attribution. If you do adopt it please be aware of a couple of things: 1) There is a bug which manifests itself for very small EEPROMs (which have 32-byte pages rather than the more common 64- or 128-byte pages). I have a fix[1] (which splits large writes into 32-byte chunks) but have not pushed it to GitHub[2] yet. 2) I intend to add support for large (1Mbit) EEPROMs later this month when I expect to have hardware to test with. > but on the other hand, I don't think > having 2 competing apps for programming FX devices, that are both based > on libusbx, will be that bad for FX users. If anything, it'll give them > more choice, and more features to pick from. Agreed. - Chris [1]http://pastebin.com/raw.php?i=MbnW4XNw [2]https://github.com/makestuff/libfx2loader/blob/master/firmware/prom.c#L207 ------------------------------------------------------------------------------ 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
