Comment by leoedin
10 hours ago
I've been working on embedded systems using iMX8s, and it's equally awful. You have to maintain your own fork of UBoot. You have to spend hours tweaking device trees. The "NXP" kernel is out of date and never updated, the mainline kernel is missing loads of drivers.
Meanwhile in x86 land you can just download a distro and boot it. Secure boot works out of the box. It's night and day.
Yup. I remember my dismay when I started working with Linux on arm boards and realizing the absolute massive gap between the hardware vendor claims of "full linux support" and the reality.
Sometimes the SDK is a zip of the developer workspace in a pseudo working state with no clear records of all that's been patched.
Vendors providing binary only kernel and system images containing god knows what is not uncommon either.
I'm convinced now that arm hardware vendors are simply incapable of even understanding what proper software support is. I'm sure some of their devs do their best but management does not care. By the time the chip ships, efforts move to making the next thing so they never properly finish the software side.
Have you looked at SoCs supported by Linaro?
Linaro is (or was, back when I was involved ~10 years ago) non-profit sponsored by SoC vendors to develop, maintain and upstream SoC support for Linux, along with running a comprehensive validation lab for all the boards they support.
A list of manufacturers did change a few times, and it was half-sponsored by ARM directly.
Every time I have watched Linaro presentations, I mostly got the feeling that their customers so top speak are embedded (Automobile and co) and Android OEMs, not so much people that would like to some day have GNU/Linux on ARM desktops/laptops.
Even rather mainstream stuff like the RPi can get wonky in places, and still people comment on why "idiots" buy RPis when this-or-that ARM board has 10% more bang for the buck. Eh, yeah, of course. I'd love to only ever run RandomShenzenCorp's heavily patched vendor kernel from 2016.
I don’t hear people suggesting to replace an RPi with a similar device (OrangePi or what not).
What I hear a _lot_ is that the thing could have been an esp32 (or Arduino rarely).
That’s a way wider price gap. I can order Costco-sized lots of esp32’s for the price of a single RPi.
RPis pricing has really, really narrowed the space where their products make sense. Low power devices can be esp32, high power can be x86 NUC things (or interconnected esp32s if you need tons of pins).
I don’t encounter a ton of things in “too big for an esp32 but I’m positive I don’t even want the option of a beefier x86 CPU”.
No hate if it works for you. I don’t even dislike RPi, they’re just in a narrower band for me these days.
RockChip stuff tends to have good support, and in fact I'd trust it more to have good support than Raspberry Pi (Broadcom). When in doubt, check or wait before buying in any case. In many cases support will not meaningfully improve from how it was at release (learned this one the hard way) and most ARM devices are e-waste. Try not to get excited about theoretical hardware specs either, they might as well be fake because of how poorly the majority of ARM stuff actually works. Go for known good software support and then upgrade to new hardware when you find something newer with known good software support a few years later.
Just in case anyone unfamiliar reads this, the way to run ARM boards is e.g. https://armbian.com/ (or NetBSD, Debian, whatever you prefer) and never the vendor junk.
RasPi just enshittified, pushing out a firmware upgrade that bricks the Pi if it detects you've upgraded the RAM yourself.