On 2012.09.04 10:27, Chris McClelland wrote: > 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.
As somewhat of a license and GPLv3 zealot, I'd be very uncomfortable asking you to change your license. You created the software, it's only fair that you get to choose the license that governs it. Also, I don't see much of a problem having a GPLv3 binary blob (or GPLv3 sample) along an LGPLv2.1 library, so while the offer is appreciated, there's no reason for you to allow a license change. Besides, the more GPLv3 software there is out there, the better! > 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. OK. I doubt many people will have a chance to be affected by it before you get your fix in (and we update any firmware we provide with our sample) > 2) I intend to add support for large (1Mbit) EEPROMs later this month > when I expect to have hardware to test with. Sounds good too! Regards, /Pete ------------------------------------------------------------------------------ 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
