Re: Impact of dropping QEMU emulation on 32-bit hosts ? (~Fedora 33)
Does anyone know of, or have, any critical/important use cases that
would
be disrupted by QEMU dropping 32-bit *host* support ? If so, let me know
here & I can forward feedback on. Or feel free to go direct to QEMU thread
upstream.
I am not a real user of ARM 32-bit. I just checked information for ARM
32-bit (armv7) use cases.
## Raspberry Pi
https://en.wikipedia.org/wiki/Raspberry_Pi
The earlier V1.1 model of the Raspberry Pi 2 used a Broadcom BCM2836 SoC with a 900 MHz
32-bit, quad-core ARM Cortex-A7 processor, with 256 KB shared L2 cache.
https://www.raspberrypi.org/blog/raspberry-pi-2-on-sale/
It seems that the version 1.1 is the last model for 32-bit, and the
announcement was 5 August 2015.
I assume a considerable number of people using ARM 32-bit Raspberry Pi.
## Running Linux on smart phone device.
Some articles about it.
* https://developers.redhat.com/blog/2017/03/16/installing-linux-on-an-andr...
* https://www.quora.com/How-can-I-install-Fedora-on-my-smartphone
ARMv7 (32-bit) was 98.1% in entire share of android hardware on March 2017.
https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg06216.html
Eventually this public don't need edge QEMU, it might keep using QEMU
v5.0.stable until all NAS/embedded devices are 64-bit...
For example, how about releasing compat-qemu50 RPM if upstream will
drop armv7 on qemu 6.x?
It's like compat-openssl10 RPM for openssl (version 1.1) RPM.
Maybe if some RPM packages need armv7 support, they can use
compat-qemu50 conditionally in the spec file.
Jun