Android Ported to RISC-V
theregister.com
Android Ported to RISC-V
1–10 of 98 posts
Re: Android Ported to RISC-V
#2Hack
Re: Android Ported to RISC-V
#3pubg
Re: Android Ported to RISC-V
#4I doubt they have the AOT compiler working. So it is probably interp-only. Combine that with the low clock speeds a d less-than-stellar IPC, I'd imagine this is a cool demo and little more.
Re: Android Ported to RISC-V
#5It is actually worrying that there will be a push to run a Google-dependent platform on RISC-V's. After all, we know that a lot of functionality is closed into Google Play Services, so that AOSP is to a great extent a bait for being fully tied to Google. Even without relying on closed-source components, you're still relying on Google's interest and good will in maintaining that project.
Instead, it's much more important to promote the "porting", or rather the adaptation, of Linux and *BSD distributions to work on RISC-V. Like with the Raspberry PI I suppose.
Re: Android Ported to RISC-V
#6urgh
Re: Android Ported to RISC-V
#7I doubt they have the AOT compiler working. So it is probably interp-only. Combine that with the low clock speeds a d less-than-stellar IPC, I'd imagine this is a cool demo and little more.
I'm not very familiar with Android but it looks like they've ported the dex2oat compiler to RISCV.
[Warning, large text file] https://raw.githubusercontent.com/T-head-Semi/aosp-riscv/mai...
Re: Android Ported to RISC-V
#8Related: https://www.cnet.com/news/chip-designer-arm-ditches-huawei-b...
Unsurprisingly, this has been done by Alibaba-owned T-Head Semiconductor. The obvious result if Chinese vendors start facing obstacles to obtain licenses to manufacture ARM-based chips (or any other non-Chinese architecture).
How can anyone expect that software/hardware-bans to global superpowers can result in anything but their software/hardware-independence in the long run?
Re: Android Ported to RISC-V
#9It is actually worrying that there will be a push to run a Google-dependent platform on RISC-V's. After all, we know that a lot of functionality is closed into Google Play Services, so that AOSP is to a great extent a bait for being fully tied to Google. Even without relying on closed-source components, you're still relying on Google's interest and good will in maintaining that project. Instead, it's much more import…
There is Huawei HarmonyOS which I believe aims to be compatible with Android mobile apps but has a different kernel and is not reliant on Google mobile services.
Re: Android Ported to RISC-V
#10It is actually worrying that there will be a push to run a Google-dependent platform on RISC-V's. After all, we know that a lot of functionality is closed into Google Play Services, so that AOSP is to a great extent a bait for being fully tied to Google. Even without relying on closed-source components, you're still relying on Google's interest and good will in maintaining that project. Instead, it's much more import…
Is there really any risk of Linux not becoming common on RISC-V as soon as a few devices get popular enough? Isn't Debian already there? And won't this help that?