An update on the Android problem

Posted Nov 10, 2017 17:11 UTC (Fri) by marcH (subscriber, #57642)
Parent article: An update on the Android problem

> Greg Kroah-Hartman started by saying that he has been working for some time with the system-on-chip (SoC) vendors to try to resolve this problem, which he blames primarily on Qualcomm for having decided not to work upstream [...] Ted Ts'o asked if there were any ARM Chromebooks that could be used as development machines;

I understand Android implies ARM most of the time, however these are still different from each other. One is software and the other hardware!

For instance Intel Chromebooks boot upstream kernels without any major issue/regression. Yet the Android container inside doesn't boot with an upstream kernel (In some cases/versions the Android container may even bring the *entire system* down: lock up, or reboot loop,...) *This* is an actual "Android problem" which has nothing to do with Qualcomm or any other ARM vendor.