LE13 Testing for RK3288, RK3328, RK3399, RK3566, RK3568, RK3576, RK3588

  • The kernel is something that moves forwards continuously and relentlessly so the adage "If you stand still, you're actually moving backwards" applies in a big way and because (for good reasons) people became inactive for a while a whole heap of WIP changes got parked for a while. I don't think there's a single series, it's more a case of "a little bit of everything" as the kernel evolved.

    Im picking up what you're putting down. As opposed to the windows way of doing things where operating systems are just stacked on top of one another forever. Where your windows 2000 program will still run through 7 shims, and if you dive too many layers deep in the menus you'll end up in a program with an unresizable tiny window from when monitors were 480p, because why would anyone ever need to resize a window 😂.


    I was just curious, I know there was an effort or push to overhaul and standardize the requirements for manipulating graphics around kms and drm to help make things less of a wild wild west. Probably pretty helpful in the long run for projects supporting wide range of devices, although painful in the short term. Especially with manufacturers of sbcs that like to play the hype release abandon cycle on repeat.

    I was helping Moonlight-qt project who lost thier HDR support because setting 1 property on 1 connector instead of atomically, the kernel just said no after a certain version. I think those changes started around 3.19 but ran parallel and weren't enforced until well into the 6.x versions. I was just curious if the rock chip HDMI was a casualty of that same standardization effort with kernel graphics coming to completion.

  • Hi, sorry to revive and old thread. I have skimmed this thread and I was wondering if there are currently RK3588 images available. The links I found in the thread are no longer there. I would like to try out LibreElec on my Radxa Rock 5B.

    I also apologise if I'm asking a silly question or if I missed a rule or guideline. I would appreciate it if you could point me in the right direction.

    TIA!

  • Hi, sorry to revive and old thread. I have skimmed this thread and I was wondering if there are currently RK3588 images available. The links I found in the thread are no longer there. I would like to try out LibreElec on my Radxa Rock 5B.

    I also apologise if I'm asking a silly question or if I missed a rule or guideline. I would appreciate it if you could point me in the right direction.

    TIA!

    https://test.libreelec.tv/13.0/Rockchip/rock-5b/
    you can find the latest nightly in this. :)

  • Nightly seems to work like a charm. Installed on my NVMe by flashing it. Came up, rebooted. Did some basic config (via keyboard / mouse / monitor), hooked it up to my TV and used the remote for the rest. Video and audio works (I'm using a soundbar). Decoding and transcoding works as well. Just had to get used to indexing of Kodi (it is more strict than Jellyfin), but I can deal with that.


    Thanks for all the work to get this running on RK3588!

  • hello ,


    it might have been answered already, but is there already av1 decode support on rk3576/rk3588, or is the userbase too small fro quick progress? might have pickedup a rock pi5a,but now it seem the train is bit gone for awhile; but for libreelec also a 4gb variant could suffice?

  • AV1 is supported upstream on RK3588 but not RK3576; the latter has a different (all new) IP block and nobody wrote drivers yet.

    And the train is indeed a little quiet. Curating a working image still requires a large number of patches and as some of the in-flight series have iterated/progressed the number of conflicts between things has gone up, and resolving and figuring out how to solve those problems requires a level of effort that I don't have time and motivation for at the moment. Things are at the stage where the easy option is just leaving things as-is until more of the major bits are merged upstream and the overall patch count reduces to a more manageable level. That probably doesn't play well with the likely timeline for K22/LE13 though. Catch22.

    LE runs happily on 2GB boards unless you're planning to run flatpak things or other services in the background. 4GB is fine.