Can some functionalities for os be passed to second kernel?
For example there could be docker or some other VM with Halium kernel to use some apps for example WiFi, camera and SIM calling?
Example can be qubesos which uses separate VM to do networking and other functions.
In the context of cell phones, it makes a lot of sense though, if you can pull it off. Android kernel for hardware support, mainline kernel for software support. Right now there’s very few phones that can run mainline linux and actually use the features people would expect from a phone, the rest use android kernels and hallium which gives good hardware support, but doesn’t support the software stack for gnome-mobile and all the ‘traditional’ linux software like flatpak apps, etc.
So you’re either stuck with a phone that doesn’t work to call, doesn’t have a working camera, etc, with mainline linux, or an android kernel that doesn’t a support the usual linux software stack and has to run something like ubuntu touch (ubports) which is great that it works, but because its ubuntu’s software stack and an android kernel, you can’t run things like gnome-mobile or other traditional linux software like flatpak apps like postmarketos can.
The main problem I’m finding is: ubuntu touch apps have to be specifically built for ubuntu touch, you can’t just grab a flatpak app like you can with postmarketos and a mainline kernel. So the app ecosystem is really lacking vs running a mainline kernel, but then of course your hardware won’t work like camera, volte, etc.
I just want a working linux phone that has access to the apps we’ve come to love, and I feel like running 2 kernels is the way to achieve that until we get more people mainlining hardware support for all the various cell phones.
Preemptively, one might question why someone would want traditional linux apps on a phone, but there’s a surprising amount of flatpak apps on flathub that are built with responsive design and scale fairly well to a phone screen/touch interface. So being able to use the same software you use on your desktop, on a phone is great!
Right, but my point is that the amount of effort required to just get the multikernel fully running on quirky phone hardware is quite a lot, and then you have to set up a lot of plumbing for both userspaces to communicate across kernels (i.e. you’ll have to write driver shims for a lot of things). It is probably easier to port software to ubports.
Yah, I mean, thats true. I guess I was hoping the multi kernel thing would be more of a 1-time development effort that would work across phones, so once you got it set up it would help all phones accomplish the same thing. I’m not a kernel dev though so I have no idea in reality how this stuff actually works under the hood.
There would be shared parts for sure, but knowing the nightmare that is phone boot environments I feel like it would need a lot of effort per device still.