That was my point. I can buy some of these chips in qty 1 on digikey, but without any documentation for the host interface I can't use them. And I don't want to sign an NDA for an open-source project.
-
-
Replying to @azonenberg
It's not clear that signing the NDA and utilizing the chip in a real design would prevent you from producing open source software which utilizes the chip in your design. You just have to ensure every bit of what you code is strictly necessary to the design and don't explain.
2 replies 0 retweets 2 likes -
Replying to @mdhardeman
Yes, but being under NDA would force you to not comment register writes, etc and generally produce poorly maintainable code. Unless you had a "secret" version of the code and then deleted the comments for the public copy.
3 replies 1 retweet 3 likes -
Replying to @azonenberg @mdhardeman
If you have a "secret" version and only publish something with the comments removed then you are in violation of clause 2 of the open source definition, i.e. it is not open source anymore.
2 replies 0 retweets 6 likes -
This seems peculiar to me. If you never made the code comments, or documented the comments elsewhere (e.g., internal docs or wiki) this would suddenly not be an issue? Likewise if you "generated" the code by hand versus using a tool and some template? Odd.
1 reply 0 retweets 0 likes -
Replying to @MartyMacGyver @oe1cxw and
It's not community-friendly to throw generated files out there as OSS (or a file with nameless registers or cryptic code)... But it seems a stretch to say its a *violation* to publish code that compiles to the same exact binaries as its internal version without its metadata.
1 reply 0 retweets 0 likes -
Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩 Retweeted Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩
Claire Xen 🏳️⚧️ 🏳️🌈 🧙🏻♀️ BLM 🏴 🚩 added,
1 reply 0 retweets 0 likes -
That's some text from OSI' Opensource Definition, but unless you are aiming to put the OSI cert logo on your software I'm not sure what legal force that's supposed to have aside from specific licenses that include that language.
1 reply 0 retweets 0 likes -
Ironic.
This is literally the definition by the people who came up with the term "open source" in early 1998 because they felt that "free software" was ill defined (different people had different opinions on what it means).2 replies 0 retweets 0 likes -
Most OSS licenses aren't really opensource by that strict definition. People use code generators, companies obscure registers, comments not meant for public consumption get redacted. It's a worthy ideal but not always feasible in practice. Which is why so many OSS licenses exist.
1 reply 0 retweets 1 like
This particular bit has nothing to do with the license. Idk what's so hard to understand here.. You can release whatever you want under any license you want. Just don't call it open source if the thing you release isn't the actual source code, even if released under OSI license.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.