Anyway, loading proprietary firmware from the eMMC image is a *feature*, because it means that it can be validated together with the rest of the OS. If you have firmware out of band, you need to perform explicit steps to verify that it hasn't been tampered with.
-
What's important to me is whether I have to reach for non-free blobs when I build software to run on the user-oriented execution unit, and whether those blobs run on that unit itself. Getting rid of blobs contained in the hardware is also important, but it's a next, distinct step
Why? Why is that important to you? Do you get digital cooties if you touch a blob? Not running blobs on the main CPU has practical advantages. Not *touching* blobs with the main CPU serves no purpose. That's just FSF religious nonsense.
-
-
It's about clear boundaries. 100% of PureOS is free software, with all the user freedom benefits it brings. If it had non-free repos with blobs, it wouldn't be true anymore. And introducing blobs into OS for devices that could very well embed it themselves is not worth it.
-
Sure, the blob is still there. But so are the blobs in all the other microcontrollers there that were already self-contained. Why make the OS "99% free plus some blobs" when you control the hardware it runs on and can maintain that boundary?
- Show replies
New conversation -
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.