3 ms·
By "can't be used" do you mean by unjustified whiners, or is there a real problem? If you're including this existing filesystem you shouldn't have any relevant
by Dylan16807 4y ago
By "can't be used" do you mean by unjustified whiners, or is there a real problem?
If you're including this existing filesystem you shouldn't have any relevant patents to worry about, and the clause about letting the user write their own firmware shouldn't be an issue for 99% of products.
Is there anything else I missed in the differences between v2 and v3?
- freemint 4y agoThe clause about letting the user write their own firmware is a huge issue for 99% of products. Use some vendor blob -> problem. Have some NDA for registers used in some hardware -> problem. Hardware does not have user firmware flashing -> problem. Legal compliance requirements for hardware bearing your name -> problem.
- Dylan16807 4y ago> Use some vendor blob -> problem. Have some NDA for registers used in some hardware -> problem. That's the same as GPLv2. If you don't mix the filesystem into your proprietary code, you don't have to reveal any of those things. > Hardware does not have user firmware flashing -> problem. GPLv3 only requires you to let the user have the same flashing ability you have. If it can't be flashed, you don't have to do anything. > Legal compliance requirements for hardware bearing your name -> problem. That's a 1% of products situation.