Yes, and no. I have an OrangePi 5 Ultra and I'm finally running a vanilla kernel on it.
Don't bother trying anything before kernel 6.18.x -- unless you are willing to stick with their 6.1.x kernel with a million+ line diff.
The u-boot environment that comes with the board is hacked up. eg: It supports an undocumented amount of extlinux.conf ... just enough that whatever Debian writes by default, breaks it. Luckily, the u-boot project does support the board and I was able to flash a newer u-boot to the boot media and then the onboard flash [1].
Now the hdmi port doesn't show anything and I use a couple of serial pins when I need to do anything before it's on-net.
--
I purchased a Rock 5T (also rk3588) and the story is similar ... but upstream support for the board is much worse. Doing a diff between device trees [2] (supplied via custom Debian image vs vanilla kernel) tells me a lot. eg: there are addresses that are different between the two.
Upstream u-boot doesn't have support for the board explicitly.
No display, serial console doesn't work after boot.
I just wanted this board for its dual 2.5Gb ethernet ports but the ports even seem buggy. It might be an issue with my ISP... they seem to think otherwise.
--
Not being able to run a vanilla kernel/u-boot is a deal-breaker for me. If I can't upgrade my kernel to deal with a vulnerability without the company existing/supporting my particular board, I'm not comfortable using it.
IMHO, these boards exist in a space somewhere between the old-embedded world (where just having a working image is enough) and the modern linux world (where one needs to be able to update/apply patches)
Hardware video decoding support for h264 and av1 just landed in 7.0 so it hasn't been a great bleeding edge experience for desktop and Plex etc users. But IMO late support is still support.
Not on this list is the current GPU Vulkan drivers Collabora are working on too. Don't think that's really blame Rockchip since they're ARM Mali-G610 GPUs, but yeah those didn't get stable in Mesa until last year.
This is the reality - most people won't spoof until they figure out it's the way to make a specific site work; and then they'll likely spoof for everything.
I'd also like to add that we forget that we're doing it, or at least I do. Once you set something up like that, there's never any reason to get rid of it; nobody is positively discriminating towards Linux.
I love when a ruleset (firewall, for example) has a "comments" field because I inevitably forget why I added something and then Chesterton's fence means I leave it forever, lest I spend hours a year later wondering why something broke.
Every time I try to change my user agent with a FF extension I get hit with brutal cloudflare captcha loops. How are you changing your user agent in a way that this is not a problem?
Actual reason: SBC retro handheld consoles now run Linux and people are using them to play steam indie games. The China holiday had some blow out pricing.
Non primary devices more likely to run Linux. Primary still windows.
Great, now we've got digital Salvia
reply