AOSP on taped-out RISC-V SoC without RVA22/23, I came back to finish... "Ruinland"
summary
Running AOSP on taped-out Qilai silicon that predates RVA22/23 requires concrete fixes: patched build system, added an Andes CPU variant, modified bionic/libunwind and NDK to disable vector use, patched ART and assembler emission to replace unsupported instructions, and recompiled a NN driver that blocked boot. Android boots on the Qilai test chip using GKI with extensions turned off, but secure TEE support and Google Play/attestation remain absent, limiting commercial app ecosystem.
AI-written summary · about
chapters (5)
- 0:00Introduction to AOSP on RISC-V
- 1:50Challenges without RVA22/23 support
- 5:49Patching AOSP components
- 7:13Why support legacy RISC-V platforms
- 9:03Missing pieces and future outlook
related talks
20mExploration of Productization of Android on RISC-V
20mChallenges in Porting Android to RISC-V
18mProgress in Porting Android onto RISC-V: Testing, Performance and Open Source
14mKeynote: The Android Open Source Project and RISC-V
38mHow to Enable Android (AOSP) on Your Developer Board- 38mHow to Enable Android (AOSP) on Your Developer Board
15mRISC-V support in Android
37mA Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP