3 ms·
It's a matter of perspective. Back in the day, CPUs didn't come with FPUs and the latter were optional co-processors. The idea in the x86-world always was to
by qayxc 6y ago
It's a matter of perspective.
Back in the day, CPUs didn't come with FPUs and the latter were optional co-processors.
The idea in the x86-world always was to "outsource" special requirements to dedicated hardware (FP co-processors, GPUs, sound cards, network cards, hardware codec cards, etc.), instead of putting them on the CPU package (like ARM-based SoCs).
So it's different philosophies entirely - tightly integrated SoCs vs versatile and flexible component-based hardware.
It's The One Ring ([ARM-based] SoCs) vs freedom of choice and modularity (PC). If I don't do simulations or 3d-modelling/rendering, I am free to choose a cheap display adapter without powerful 3D-acceleration and choose a better audio interface instead (e.g. for music production).
The SoC approach forces me to buy that fancy AI/ML-accelerator, various video codecs, and powerful graphics hardware with my CPU regardless of my needs, because the benevolent system provider (e.g. Apple) deems it fit for all...
Torvalds is just old-school in that he prefers freedom of choice and the "traditional" PC over highly integrated SoCs.
- raverbashing 6y agoFP coprocessors "only" existed because the processes weren't advanced enough to have them inside the chip, but they were a natural extension (they were married to the instruction set of the chip - it wasn't a product, it was a feature) At the old days there were minor competitors to the x87 family that died quickly. (For reference: https://en.wikipedia.org/wiki/X87#Manufacturers https://en.wikipedia.org/wiki/X87#Manufacturers ) For the rest yeah, it kinda makes sense to have them customizable.
- pjmlp 6y ago> The idea in the x86-world always was to "outsource" special requirements to dedicated hardware Actually the Atari and Amigas were there first, that was PC catching up with their multimedia capabilities.