> Our goal was to develop a single operating platform across multiple 64-bit ARMv8-A server-class SoCs from various suppliers while using the same sources to build user functionality and consistent feature set that enables customers to deploy across a range of server implementations while maintaining application compatibility.
I wonder how successful this was. Previously, all x86 CPUs (including x86_64) would bootstrap into the same mode from 1970s CPUs and preserve all the functionality from the original ISA (we still talk to the RTC via inb/outb, e.g.). I suppose this changed a little bit after EFI/UEFI was offered?
ARM CPUs were not bound to this backwards compatibility so AFAIK every vendor could implement their own bootstrapping functionality, and therefore having a single bootloader was challenging/impossible? uboot is a popular basis solution but IIRC everyone provides their own tweak to suit their SoC. Does TrustZone normalize the bootstrapping process for ARM devices such that we can write a single bootloader binary and expect it to work the same way across ARM server SoCs?
Anyone know where one can buy an ARM server to run this on?
Does anyone know the current ARM (equipment cost + ~0.9 utilization power costs) amortized over, say, three or five years compares to the latest generation of Xeon and Epyc?
I had the impression that CENTOS7.3 was available on baremetal ARM64 on scaleway since a long time. Is it really new ? Maybe I do not understand what this announce is about.
ARM64 was released on Debian and Ubuntu 5 or 6 years ago.. Why has it taken RedHat so long? They were part of the same ARM server club.