Comment Re:China (Score 2) 30
Is this due to the recent reports of China all in on RISC-V?
It's because RISC-V is currently fragmented. Not the base ISA, but the base ISA isn't enough to build a device, and there are a lot of divergent extensions.
That wasn't a problem when RISC-V was only theoretical, but now that companies are working towards actual devices, having the "common" RISC-V support in the Android Common Kernel was a hindrance, not a help. The expectation is that over the course of a few years the RISC-V Android ecosystem will coalesce and settle on a common set of extensions to the ISA and it will then be possible to standardize the RISC-V support in ACK. Until then, it's better if ACK doesn't have any RISC-V support so chip vendors and OEMs can straightforwardly patch in what they need.
I should mention that although I'm an Android engineer, I don't have any significant contact with RISC-V work. The above is my interpretation of the public comments, in light of what I do know about the state of RISC-V and the way the Android ecosystem is structured and works.