No mini PC can beat most things about the Pi, apart from performance and compatibility, the latter of which is fully the fault of the manufacturer.
Rpi is strictly suited to very specific use cases.
My new favourite tool for these situations is the Radxa X4, which is the exact dimensions of a RPi, but with an Intel x86 CPU and an onboard microcontroller to drive GPIOs.
Will checkout the radxa x4 sounds interesting.
https://www.reddit.com/r/OrangePI/comments/1buzts4/uboot_v20...
The board boots Armbian fine with nothing connected to the serial port.
[1] https://github.com/Joshua-Riek/ubuntu-rockchip/issues/1073
The Raspberry Pi 5 and Orange Pi 5 are just too expensive. I do have some of the Pi 5s from both these companies, but have replaced them with Intel N100 mini-PCs instead. But I'll still use RPi 4's for my 3d printers and other lower-end uses.
And RPi's software support is just better: I've got an Orange Pi 4. Orange Pi hasn't updated their OS for it in years. Last time I tried to get it working in Armbian, HDMI output was (is?) broken: https://forum.armbian.com/topic/26818-opi-4-lts-no-hdmi-outp...
For me personally, much of the value of the RPI products is knowing they will have long term support.
RockChip really only appears to care about embedded auto apps etc...thus their support horizon is more about sustainment and not enhancement, and they do little to support the community.
I can get this for the RK3588 though there are problems with my Orange Pi board that uses it.
How do you figure? E.g. OpenWRT, Ubuntu, Alpine Linux, Kali, and Zephyr all offer official image support. Others have unofficial support, e.g. I think FreeBSD actually falls in this boat.
A 10 year old celeron n2930 based mini pc i purchased for 30$ at a scrapper performs way better than the pi4. Ran esxi and bunch of vms on top of it aswell. Sips 10 w of power.
And all other os's run terribly on the pi. I tried running ubuntu via a usb nvme drive and it was laggy.
Too underpowered for the price it sells for. I tried streaming some live data on 2 tabs and the pi4(4 gig version) started stuttering.
If only we could have somehow predicted this. I mean who could have predicted that a company that has never released hardware documentation and screwed over individual users in preference to corporate users during shortages would get in the way of porting other OSes. <shocked Pikachu face>
I mean, it's not like people have been bitching about this for more than a goddamn decade.
If only we could have forseen this <rolls eyes>.
An RPI5 4GB is exactly the same price and form factor as the Beagle Y-AI. You can help the folks trying to do this right or not. The choice is yours.
It seems the ARM SystemReady stuff is only for big iron.
In theory, it's a wonderful idea, because it means you can run the same distro on your RPis as on the rest of your fleet (architecture differences notwithstanding), and therefore have consistent patching requirements, etc. In practice, as frustrating as it is that the RPi kernel patches haven't been upstreamed, they exist for a reason and I think by not having them, you're shooting yourself in the foot (even if you only hit a toe or two). Two things I observed recently when directly comparing stock Debian aarch64 with Raspberry Pi OS on an RPi4 was a 40%+ reduction in SD card read performance, and nonfunctional power control of the USB ports.
Fwiw I still have a “poor man's NAS” RPi4 running Debian, and it works great. (The SD card throughput deficiencies don't affect me there because the system boots from a USB-attached SSD.) If you're able to take the time to make a situation-specific assessment of what works (and what works “well enough”) vs. what doesn't, then in the long term, you can reap the benefits of not having to remember how to handle a single oddball OS in your fleet (especially given RPi OS' particularly consumer-oriented whims).
An interesting further little feature of TianoCore particularly for Pi 4 users is that it maintains a fake hardware clock. It only ticks forward when the firmware is in boot services mode; it is persisted to the firmware's own image file in the EFI System Partition; and it isn't as effective as even a simple fake-hwclock utility. But it does satisfy the operating systems that assume that there must be a hardware clock, because every computer is PC98-compatible.
> So the question that comes to my mind is whether this is yet further new and different Raspberry Pi 5 hardware that comes with no software or prospect of software.
If by “this” you mean the MicroSD Express hat from the article: this is a hobby project produced by a hobbyist, who seems to have no plans to sell or mass produce it.
It is unfair to the creator for you to lump it in with, and draw a conclusion from, the works produced by Raspberry Pi Holdings.
The Raspberry Pi 5 is lacking in some fairly basic support that the Pi 4 has. There's no TianoCore, no NetBSD, no FreeBSD, no OpenBSD, no OmniOS(CE) … in fact nothing at all apart from Raspberry Pi OS. A couple of of the operating systems seem to point the finger at poorly documented hardware changes that the manufacturer has been no help with.
* https://github.com/tianocore/edk2-platforms/tree/master/Plat...
* https://wiki.netbsd.org/ports/evbarm/raspberry_pi/#index6h2
* https://www.freebsd.org/where/#download
* https://www.openbsd.org/arm64.html
* https://downloads.omnios.org/media/braich/
So the question that comes to my mind is whether this is yet further new and different Raspberry Pi 5 hardware that comes with no software or prospect of software.