3 ms·
It's an interesting edge case when you have someone actually moving from one model to another. But I think even OpenBSD's famously strong policy on binary blobs
by _delirium 15y ago
It's an interesting edge case when you have someone actually moving from one model to another. But I think even OpenBSD's famously strong policy on binary blobs would allow this one, at least as they've implemented the policy in the past. They require source for drivers, which means anything you need to load onto the chip or use to communicate with it, but not for every piece of ROM that's internal to a chip. For example, Intel and AMD both microcode some instructions in firmware on their chips, rather than implementing them in silicon, and OpenBSD is ok with that, treating the silicon and microcoded part as all part of the blackbox chip package, rather than as a "driver" that requires source.
- tedunangst 15y agoActually, the requirement for adding firmware (something that is loaded onto a chip) to OpenBSD is that it be modifiable. Source isn't required. (Speaking only about firmware that goes on the chip, not HAL layers that run on the CPU. Those are banned in binary form.) I'd say the biggest difference here is that OpenBSD's goal is to make a free operating system, not a free phone.