So moving out of the x86/x86_64 world is really a no-brainer: why would all the electronic giants keep paying for x86 when they can get out of the de-facto duopoly? It seems that they are settling on ARM (Amazon Graviton, Fujitsu A64FX, Apple A12Z, etc.). It could have been another architecture, but it couldn't be x86_64.
On the other hand, there are other architectures besides ARM and x86: RISC-V, OpenSPARC, etc. Maybe one of these would be better for developers who don't want to deal with the ARM landscape fragmentation.
I do appreciate that the x64 is more recent and will still be patented to heck - but there's only 3 more years until the first of those expire, methinks.
PAE for x86 means that programs needing more than 4GiB of main-memory can be run without needing a true 64-bit ISA - and PAE won't be patented anymore as that was introduced around 1995.
I don't disagree with you, but is that really a world developers or even consumers want? A world where each device manufacturer creates their own chip based around arm's processor designs that's incompatible with the next device's chip despite being virtually identical?
You're right, as a corporation looking to make money off all aspects of everything, it's a no brainer. For everyone else, it's a worse situation than the processor fragmentation of the 80's and early 90's.
X86_64, amd and intel, took advantage of the situation of the time and provided a somewhat standard, though controlled by them, processor design that allowed tons of individuals and companies to flourish. Moving to yet another highly controlled set of fragmented platforms is a step back to the 80's.
Ideally, we should be moving forward towards a system that provides a universal set of instructions licensable by all, without allowing licensees to restrict their implementations.
There's a lot of problems with our current paradigm but backpedaling to an even more controlled and fragmented platform is not the solution.
I really believe open hardware is a serious issue that's only starting to be addressed, meanwhile big established players are making their moves to stop it.
Arm is a big established player, one of the biggest, they may not be as forward facing as Microsoft or Apple or google, but damn does that company have a huge influence on everything.
Widely adopted open standards for hardware that does not encourage proprietary licences on basic chip design is a definite no brainer on the way forward.
The hurdles that need to be crossed though are greater than with software. Real tangible goods that require manufacturing require tons of overhead and complexity. This challenge is something I feel is the open source idealogy's next great obstacle and overcoming it will open computing so much more than even open source software has for the world. But, only if people has a whole come together and work towards it by not accepting anything less.
Your vision of an open ISA like RISC-V winning is something that I mainly see benefiting manufacturers making closed hardware, not people who want general purpose hardware for running general purpose operating systems. For example Western Digital and nvidia are going to be using RISC-V as part of every SSD/HDD and GPU, but we will not get to run our own code on them. There are also hardware vendors selling RISC-V microcontrollers, but nothing that could run Linux or BSD, even SiFive only has Arduino-level boards out (they had Linux-capable ones but don't seem to be making more of them for sale). Eventually there might be a RISC-V entry in the SBC market, but I think ARM is still going to own that market for a long time.
[1] https://www.crowdsupply.com/microchip/polarfire-soc-icicle-k...
That used to be true, but I dont know how true it is now.
Once upon a time, ISA and ATA were both wired right to the bus.
By the P3/Athlon era everything was probably on a super-io controller and or south bridge, but that communication towards the northbridge/CPU was over PCI or ever fancier links.
But the clear cutting point to me is EFI. Most of the standards in how things communicate on older PCs was more based on the IBM BIOS. Early clones couldnt exist until that was nailed down. But... EFI replaces all of that with a new abstraction.
Note, however, that there's a lot of "quirks" and similar device-specific corrections for x86 as well. These get presented to Microsoft by the manufacturer, and Linux gets to reverse-engineer them.
I was aware of being able to have ex. u-boot pass a device tree file to the kernel at boot time; are you talking about that, or something more generic?
What I think is interesting is what this will do to the low-power x86 front, not just in terms of technical innovation but also availability. I'm perfect content building for x86, if it becomes as-available as the raspberry-pi class of devices ...
I understand power usage is a big concern these days, but I can't help but feel this aspect of arm is greatly overlooked and that the push towards arm devices is also partially inspired by the ability to lock down chip designs to a greater capacity than x86_64 chips.
Just look at the existing fragmentation among arm powered devices as is. I don't really like the thought of what an arm powered future could look like.
I really wish I could remember what video it was, but I remember years ago watching the ceo of arm present a new chip with built in emulation technology, that theoretically, would have allowed multiple operating systems to run at once or something. I remember the person talking to him asked if he forsaw this as the future, and he just laughed and said oh no, no manufacturers would never dream of allowing this and furthermore they'll likely use this technology to further specialize and lockdown their chips.
It may be personal bias, but since then and other things i've learned about arm, I've just had this lingering unease as to what them gaining dominance would mean to general computing.