2 ms·
Just to expand slightly, "proprietary" in the sense of "built by us for this computer," but not in the way that free or open source software developers speak of
by steveklabnik 3y ago
Just to expand slightly, "proprietary" in the sense of "built by us for this computer," but not in the way that free or open source software developers speak of the word "proprietary," the vast majority of what we do is MPL licensed, to the degree that it is actually possbile.
- lytedev 3y agoOut of curiosity, is there a list of those things that can not ot could not be licensed thusly and why?
- bcantrill 3y agoIn some cases, it's derived work of open source but non-MPL'd code -- but the ones that Steve is referring to are where we have third-party proprietary firmware. There aren't a ton of these (and in almost all cases, we ourselves don't have source code). We have (naturally) tried to minimize these, but as a concrete example: every AMD CPU has a PSP that runs proprietary software; we deliver that as a binary blob given to us by AMD (it's delivered over SPI to the host CPU).
- deleted 3y ago[deleted]
- morganw 3y agoCan you expand on what is not MPL licensed? I recall (foggily) reading about struggles with incomplete data sheets for Nuvoton controllers & I see the discussion about CVEs for NXP microcontrollers with secret patch ROMs.
- steveklabnik 3y agoSee Brian’s excellent reply to your sibling.