I have always wanted to learn to build a (relatively modern) computer like the one you described:
- Some 32-bit CPU, whatever, anything that is a bit easy to program through C/ASM, just to make sure there is no weird kirks.
- Support keyboards, displays, mouse, etc., just the usual ones. So a lot of drivers.
- Some 256MB - 512MB memory should be good enough.
- Has an OS, some programming languages, some tools, a good editor, etc.
This is like the Ben Eater 8-bit computer in adrenaline. It is probably a LOT of work just to figure out how to source the correct components, and build the thing, then a LOT more work to write drivers for them, and MORE work to write OS and compilers and tools for them. We can't use Linux because it has memory protection all over the place. We need something that newbies can poke and peek into, and simply reset the CPU if something is wrong, just like the micro computers in the 70s/80s. We DO want capable compilers and interpreters (e.g. C/Python) and good tools (like, some editors that have good auto-complete at least).
It's a bit like building a pad or a mobile phone, but without all those commercial consideration. Nowadays, to build a pad or a mobile phone, if I'm not mistaken, one simply push Android into the chipsets and call it a day, which is not what I want. But what I want probably doesn't make $$ so no one is going to do it.
> Support keyboards, displays, mouse, etc., just the usual ones. So a lot of drivers.
You wouldn’t even need that if you released it as an all-in-one like the hobbyist machines of yore (C64, speccy, etc). Just give it a relatively decent cherry MX built-in with swappable keyblocks. Add a USB hub for HID devices and include a basic HID driver, and include HDMI.
- Some 32-bit CPU, whatever, anything that is a bit easy to program through C/ASM, just to make sure there is no weird kirks.
- Support keyboards, displays, mouse, etc., just the usual ones. So a lot of drivers.
- Some 256MB - 512MB memory should be good enough.
- Has an OS, some programming languages, some tools, a good editor, etc.
This is like the Ben Eater 8-bit computer in adrenaline. It is probably a LOT of work just to figure out how to source the correct components, and build the thing, then a LOT more work to write drivers for them, and MORE work to write OS and compilers and tools for them. We can't use Linux because it has memory protection all over the place. We need something that newbies can poke and peek into, and simply reset the CPU if something is wrong, just like the micro computers in the 70s/80s. We DO want capable compilers and interpreters (e.g. C/Python) and good tools (like, some editors that have good auto-complete at least).
It's a bit like building a pad or a mobile phone, but without all those commercial consideration. Nowadays, to build a pad or a mobile phone, if I'm not mistaken, one simply push Android into the chipsets and call it a day, which is not what I want. But what I want probably doesn't make $$ so no one is going to do it.