> Also, does this require across the stack changes? i.e. not just OS ones.
I'm not sure where you draw the boundary between 'stack' and 'os'. Can you expand a bit?
Do you have any links? I'm curious, and not a little bit skeptical about the near-term competitiveness of RISC-V in the mobile space.
https://news.ycombinator.com/item?id=37924092
https://news.ycombinator.com/item?id=37919907
It doesn't exactly sound imminent.
Mostly Chinese companies have been very busy designing & manufacturing actual silicon. And prices for such products have come down a lot, too.
It wouldn't surprise me if at some point there's RISC-V based phones, tablets & other devices on Chinese market, that most people outside China simply don't know about.
Or that teardown of a cheap phone sold in say, India, turns out to have a RISC-V SoC inside without much public attention beforehand.
Probably sooner than later. RISC-V is bound to become a lowest common denominator for computing devices especially at the low end. Picked by default unless <insert specific requirement here>.
Android being ported is a logical consequence of this.
It typically takes 2-3 years from core announcement to being in an SoC for a high end phone.
They are coming.
Arm will have something newer by then, of course, but a 2023 flagship Galaxy S23 is not going to look stupid in 2026.
Haven't tried the AOSP port for the LiCheePi 4a yet. Probably should give it a whirl just to see if things just work.
That's easier just to try downloading Minecraft through the Play Store than boot strapping the entire toolchain needed to get PolyMC working.