This is truly massive. Extending the "power of boring" beyond servers to other footprints.
SystemReady SR is what used to be called ServerReady.
SystemReady ES (Embedded ServerReady) is the new spec that enables operating systems like @VMware@esxi_arm or @Windows to boot on non-server 64-bit Arm platforms.
And what's that? The first system to be certified the Raspberry Pi? Yeah baby.
Shit just got very real - the most popular Arm SBC is no longer a weird silo! Time to update the rpi4-uefi.dev site 😀.
In fact, the Pi collab between @Arm and @VMware kick-started the SystemReady spec work.
And it's not academic, some of the @Arm folks even got CPPC (Collaborative Processor Performance Control) working. Obviously much work remains to be done, but we've just put the massive @Raspberry_Pi ecosystem on collaboration track with the big iron, not a collision course.
I meant to type “another”, not “any” 🤦♂️
• • •
Missing some Tweet in this thread? You can try to
force a refresh
@esxi_arm Yup! Getting firmware working and polished is a massive massive undertaking. One that I and a very special set of folks from around the world have been driving over the course of a few years now. All as a side act.
@esxi_arm It all started in 2016, when Microsoft put out Windows 10 IoT for Pi 2/3 and released the sources to their TianoCore modifications github.com/ms-iot/RPi-UEFI
@esxi_arm In 2017, Ard Biesheuvel separately developed an early port of 64-bit UEFI support. And this one had PSCI (via TF-A, then called ATF).
Note that this has nothing to do with CIFS. Nothing at all. But it speaks volumes about the developer investment in supporting NFS vs CIFS clients in Linux.
I've been a corp citizen for 15 years now. I've learned that most meetings really can and should be an email.
1:1 meetings are good - they are the quickest way to sort out any kind of a question, discussion or argument. If you send an email, and the reply comes back with more questions than you had statements - time for a call. Don't play email tag.