Chris Cappuccio [ch...@nmedia.net] wrote: > openda...@hushmail.com [openda...@hushmail.com] wrote: > > Hi, > > > > What are the ups and downs of replacing Linux with OpenBSD in Google's > > Android operating system? I guess this question would apply to the new > > Sailfish OS as well. > > OpenBSD is designed for mobile phones. Of course Google should have used it.
Ok instead of my stupid smartass answer. How about this: 1. OpenBSD now includes KMS and could support systems like Wayland that, in theory, are probably better suited for mobile (or any modern graphics in general) than X11 (At least, the Nokia developer who spent years hacking X11 into the N900 series thinks so) 2. OpenBSD has a license that is well suited for inclusion into devices, even more so than GPLv2 (Although most manufacturers don't seem to mind the GPLv2 because Linus built in various exceptions into his model) 3. The chips that support these various phones are all proprietary, undocumented, and the manufacturers only produce support blobs to match the Linus licensing model and the Linux kernel on these devices. 4. OpenBSD has a tight and compact model that should be easy for embedded developers to embrace 5. OpenBSD does not currently do much to support various phones although it does have ever increasing support for ARMv7 chipsets which is what all of them run on (that and ARMv8 now) Obviously the biggest hurdle is #3 and of course someone has to have the interest, which is invariably going to be a manufacturer, and currently manufacturers embrace Linux, because it has a lot of knowledge/attention/momentum in this area. So the next question is, why would someone want to switch to OpenBSD on one of these platforms? 1. Concise ecosystem (less maintenance of your own distribution) 2. High quality code 3. Increasing attention to areas that matter (ARMv7, KMS, etc)
