3 ms·
I've been dealing with silicon vendors (Intel, AMD, some ARM implementers, a couple of other folks) on the subject of open source firmware (as in: GPLv2) for 15
by pgeorgi 3y ago
I've been dealing with silicon vendors (Intel, AMD, some ARM implementers, a couple of other folks) on the subject of open source firmware (as in: GPLv2) for 15 years (as in: tirelessly). I've been arguing against locked boot processes behind the scenes and in public (e.g. https://patrick.georgi.family/2015/02/17/intel-boot-guard/ https://patrick.georgi.family/2015/02/17/intel-boot-guard/). I held talks at coreboot conferences, even though I despise the spotlight.
That said: 15 years of activity is a lot of work to unpack in "specific terms", so "unspecified terminology" that still provides a rough overview it is.
- sobkas 3y ago> That said: 15 years of activity is a lot of work to unpack in "specific terms", so "unspecified terminology" that still provides a rough overview it is. How about list of open firmware(preferably consumer grade, big corps can get it anyway) that you helped or developed? And if it is so good, why more and more hardware needs closed firmware?
- pgeorgi 3y agoThe relevant firmware project to answer here is coreboot: My contributions range from technical contributions (see git log, ~3.5% of commits are mine, as poor a benchmark as that is) to support in our forums to documentation to behind-the-scenes work that keeps the community together or pushes back against even more blobs. As for "why more and more hardware needs closed firmware": In 2005, which PC started from open source firmware, outside select data center deployments?
- pabs3 3y agoAny chance you can get some movement inside Intel on the Sound Open Firmware user-signing issue? https://github.com/thesofproject/sof/issues/5814 https://github.com/thesofproject/sof/issues/5814