Am Dienstag, den 28.04.2020, 14:30 +0100 schrieb Marc Zyngier:
Hi,
well, the PCBs are currently in production, the cases are already here (coating is currently being delayed as the company has closed down due to Corona right now), so the first 500 units would be ready to be shipped in around 2 - 3 months at latest.
The non-existance problem would therefore be solved then.
So far, AFAIK, the Letux team has tried their best to get as close to possible to mainline kernel and support as many classic devices (OMAP3 and OMAP4 devices as well), so removing 32bit support from mainline would surely be a step back for a lot of older devices as well.
I know we have to accept the decision, but so far, I've known Linux to support as many older devices as possible as well - removing KVM Host 32bit support would be a step back here.
Is there a specific reason for that? Is it too complex to maintain alongside the aarch64 KVM Host?
Hi Lukas,
Thanks for your email.
On 2020-04-28 13:38, Lukas Straub wrote:
Hello Everyone, As a preorder of the Pyra handheld, (OMAP5 SoC with 2x cortex-a15 arm cores) I'm against removing KVM host support for aarch32. I'm probably going to use this device for more than 5 years and thus the latest lts-kernel is no option for me.
So let me spell it out. You are against the removal of a feature that you don't use yet, that you may of may not use on a device that doesn't exist yet, which you may or may not still be using by the time 5.4/5.6 aren't supported anymore. You don't seem to have the strongest case, I'm afraid.
But nothing is lost! The code is still in the git tree, ou can always revert the removal patches and revive the port if you are so inclined. It will just need to be stand-alone, and not depend on the arm64 code, which is now evolving its own separate way.
Cheers,
M.