5 ms·
Yeah but who, other than the person responsible for the firmware that boots the system, cares? These simplifications will have zero observable benefits to you.
by jeffbee 3y ago
Yeah but who, other than the person responsible for the firmware that boots the system, cares? These simplifications will have zero observable benefits to you. They won’t save a lot of die space or cost.
The complexity of the far past is so small that it is inconsequential today. The PS1 was implemented in spare die area of the PS2’s USB controller. Time marches on and die space becomes free.
- kibwen 3y agoTrue that it's invisible to end-users, but it's still a pain in the ass to people writing OSes. Lowering the barrier to entry even a little bit will be appreciated by hobbyists.
- t0b1 3y agoHow so? The bootloader already runs in long mode with UEFI and it also takes care of bringing up other cores so this is not really a problem in my experience.
- JoshTriplett 3y agoLinux still needs to use a Startup IPI to bring up other CPUs, which starts them running in 16-bit mode at an address under 1MB. Having a fully 64-bit way to bring up other CPUs would simplify that.
- monocasa 3y agoUEFI doesn't really take care of bringing up the other cores. There's a way to get access to them, but you have to give them back to UEFI before exiting boot services, so that doesn't really help your kernel. You still need to do the SIPI into x86-16 code to really take control of the AP cores. Even the new way (that isn't actually implemented AFAIK) just SIPIs into long mode code, it doesn't use the UEFI multicore stuff.
- DSMan195276 3y agoFrom a hobbies point of view I'd actually argue the opposite. The nice thing about the old stuff (Ex. the 8259 PIC support they're removing here) is that it's much simpler to get going. They have very large limitations, but those don't matter when just starting, and they serve as a good stepping stone and learning opportunity before eventually moving on to the modern and more complicated stuff. Additionally if you're using a bootloader then the bulk of this is already solved for you anyway.
- rbanffy 3y agoThe modern stuff is only more complicated because it had to be built around and on top of dozens of dead civilisations under it.
- hulitu 3y agoThis is the simplistic explanation. I think that besides that, some people are paid for complexity. That would justify the evolution of SW in the last 10 years.
- jkingsman 3y ago> The PS1 was implemented in spare die area of the PS2’s USB controller Whoah, that is WILD. Any info about where I can learn more about this?
- nateguchi 3y agohttps://www.copetti.org/writings/consoles/playstation-2/ https://www.copetti.org/writings/consoles/playstation-2/ Under heading “I/O”
- tobz1000 3y agoIt sounds more like the I/O firmware was running on dedicated PS1 hardware: https://www.theguardian.com/technology/2013/dec/12/ps4-and-xbox-one-so-why-arent-they-backwards-compatible https://www.theguardian.com/technology/2013/dec/12/ps4-and-x... > The PlayStation 2, meanwhile, had the original PlayStation chipset built in, so it ran pretty much any PSone title – and when that chip wasn't being used for backwards compatibility it doubled as an input/output processor, which was pretty canny.
- helf 3y agoI can't find anything claiming this. This is literally the first time I have ever seen this claim. The original fat PS2 including majority of the PS1 hardware physically in the machine. More and more of it got offloaded to pure software emulation with later model revisions. I, too, would like to see info on this supposed "spare die space on the USB controller" claim. Because it would be really neat if true lol
- mikeponders 3y agohttps://www.copetti.org/writings/consoles/playstation-2/#io https://www.copetti.org/writings/consoles/playstation-2/#io Essentially the thicc PS2s include the PS1 chip and normally use it for IO and also for PS1 compatibility.
- meepmorp 3y ago> The PS1 was implemented in spare die area of the PS2’s USB controller. This really confused me until figured out you weren't talking about the IBM PS/1 and PS/2.
- Narishma 3y agoI don't think they are. IBM PS/2 was more than a decade before USB. But then, the PS2 console didn't have USB either, so I'm not sure what they're talking about.
- shpx 3y agoI care. I want to learn the entire thing I'm using, which means I appreciate things that are simpler and faster to learn. You can say I am a stupid or irrational person not worthy of consideration for wanting this but I am who I am and I want to spend money on computers that cater to me.
- tedunangst 3y agoDo you want a computer architecture that replaces and obsoletes everything you've previously learned or one that evolves and adds new features on top?
- solarmist 3y agoEither depending on the situation.
- bdamm 3y agoThen you are obviously running OpenBSD on ARM.
- jacquesm 3y agoIn that case you should probably not look at x86 at all. It's one of the most convoluted architectures out there, especially because it lugs all of that legacy stuff along.
- phendrenad2 3y agoWhen people say "who cares?" they generally mean "what non-vanishingly-small percentage of people care?" and I think that's still an unanswered question!
- citrin_ru 3y agoIt very similar to chip die space - modern technologies are so complex that to learn how 8086 works is a very small effort compare to learning how the latest intel CPUs work. And emulation of older generations is a small part of this complexity.
- 3y ago
- amluto 3y agoThe OS cares, sadly. When the OS, running one one CPU, instructs another CPU to start (which happens — your system boots into your OS and also resumes from suspend with only one CPU running OS code), it sends a message called SIPI to that CPU. The CPU responds by running OS code, in real mode, at an address <1MB. So the OS needs to find valid memory below 640kB that doesn’t conflict with any other horrible legacy use. Also, the “LA57” 5-level page table design has a little whoopsie: you can’t switch between 4 and 5 level page tables without exiting paged mode entirely.
- q1w2 3y agoWhile all true, obviating all this has no material impact on the user.