So you want to make a Raspberry Pi killer
jeffgeerling.com
jeffgeerling.com
Or basic driver support? I have an orange pizzle and it has a software mouse cursor with mind blowing amounts of flicker. Hardware cursor was a solved problem 30 years, wtf is this???
edit: Also, on Windows, you can notice the presence of the hardware cursor because Windows has an additional trick: it will switch to a software cursor when dragging windows, so that the window and the cursor stay synced up. However, since it doesn't perfectly sync the hardware cursor turning off with the software cursor frame being presented, you'll usually see a very subtle flicker when you first start dragging a window. I dunno if this still applies to fully-updated Windows, but it still applied last I checked, in Windows 10. (And once you notice this, boy, you never stop noticing it. It takes a second.. then it's hard to ever not see it again.)
That's pretty interesting, I played with that and did notice it.
Also from googling if you set 'MouseTrails' to -1 in the registry it's a hack which disables the hardware cursor, not sure if that's still current.
A lot of times the smaller hardware-driven companies (who may charge $3000+ for a Pi-integrated solution) have very robust hardware... and software that I'm surprised works at all.
Yocto is not as great as it seems. You can go a long way with stock Armbian.
You can either pay real prices or you can bitch and whine when the RPi overlords allocate your chips to people who pay real money.
Those of us who get this already use something else.
The key, indeed, is software, documentation, ease of use.
What is the 'something else' that you would recommend?
I know someone with an Orange Pi 5 and everything he needs works, except the GPU. A lot of SBCs are fine if all you want to do is run headless software on them. The armbian images come with reasonably good hardware drivers. But now that panfrost has stopped development for the newest generation of Mali GPUs, there is no hope for the Orange Pi 5 to be anything, but a paperweight.
> - The quirky VideoCore GPU-based boot process (see first point)
I mention that regarding the Pi, but sometimes the opposite happens on other SBCs; there's some open / 'mainline' development that happens (usually community-driven), but at some point the manufacturer just stops caring about a board... and then it's crickets.
And you're left with hardware running outdated software or possibly someone's handcrafted distro that gets about 60% of the hardware working (hope it's the parts you need!).
The actual "elevator controller" or "e-scooter controller" or whatever would run fine on a Z80, but it has to pull something from the cloud (config file, activation unlock). Suddenly, you need a MCU big enough to talk to Wifi/BT/cellular modem, and handle TCP/IP/SSL, and you're looking at ARM and x86 parts.
Something like the "wi-fi modem" concept you see for retrocomputing might be interesting. A black-box component that handles all the connectivity, you pre-program it with the specs of the network transfer, and it exposes the controls and UI for "select wi-fi network/pair bluetooth/etc". On the MCU's side, it would just have a very basic serial or parallel interface, that 8-bit tooling could handle easily.