Android, the operating system developed by Google, currently supports a couple of different instruction set architectures (ISAs), such as Arm and x86. Most devices that use Android, including smartphones, tablets, TVs, and smartwatches, use Arm-based chipsets. Intel stopped producing CPUs for phones, and support for MIPS was removed in NDK revision 17. However, one ISA that has a lot of chatter is Reduced Instruction Set Computer V, RISC-V, which is a free and open ISA. Anyone is free to design chips based on it without paying any licensing or royalty fees, and Google announced official support for it at the company's keynote that took place during the RISC-V Summit.

RISC-V is special because it's a free and open ISA, and vendors that want to make cheap IoT products will be interested in using RISC-V to develop low-cost chips. At the same time, companies seeking to reduce their dependence on competitors or foreign entities will also be looking in earnest. Interestingly, Google already makes use of the RISC-V architecture for its Titan M2 security chip in the Google Pixel series, and Intel is now offering to manufacture RISC-V chipsets for commercial customers.

At the company's keynote, Lars Bergstrom, Android's director of engineering, said that he wants RISC-V to be seen as a "tier-1 platform" in Android. This is on par with what Arm currently is to Android, a rather bold step to take in the face of what seemed to previously be complete disinterest from Google. The Android team, in response to ArsTechnica's Ron Amadeo when he asked the team if RISC-V support was on the cards at Google I/O 2022, seemed to suggest that RISC-V wasn't coming anytime soon. Amadeo's question regarding RISC-V support in the future was answered with "we're watching, but it would be a big change for us."

risc-v-growing-from-prototype

Bergstrom says that you can download and try a very limited version of Android for RISC-V right now, but it lacks support for the Android Runtime (ART) for Java workloads. He said he expects official emulator support to come soon, with ART to come sometime in Q1 of 2023. He shared the above slide, which shows that while there's a lot to do to get AOSP off the ground on RISC-V, the company is committed to the architecture.

The best part of all of this is that developers won't have to do a whole lot to have their apps run on RISC-V devices. ART basically "translates" bytecode into native instructions of the device that it's running on, so it would be translating to RISC-V instead of Arm. Native code is a different story, but Java code makes up the entirety of most Android apps.

As for why companies may be looking to jump ship from Arm, there are a few reasons. For starters, the company has been incredibly volatile. SoftBank, its owner, tried to sell the company to Nvidia, though that fell through. As well, Arm has become a pawn of trade sanctions placed on companies like Huawei, where it was forced to cut contact for several months. Even worse still is that Arm has sued Qualcomm over its Nuvia purchase, and it's not a great look to be suing one of your biggest customers.

RISC-V is seen as an escape from western reliance, and a large part of this is because of RISC-V International's incorporation in Switzerland. It can act as a neutral party to both the US and China, making it an appealing option for companies looking to design chipsets. Alibaba is one of the biggest proponents of RISC-V, and engineers at the company ported Android 10 to a RISC-V board two years ago.

We'll be watching and waiting to see how RISC-V shapes up over the coming months. While it will likely take some time before we see viable flagship devices with RISC-V chipsets on the market, Google is opening the door for companies to certainly try.


Source: Google

Via: ArsTechnica