Is there any plans for a new image?

[Ukhupacha]

Hello everyone,

Do you know if there is going to be a new image? The last one is from oct 2024.

Just wondering, lovely work here

[Joshua-Riek]

I'd like to jump back into this project, but I'm prioritizing myself at the moment and addressing some personal issues.

When I do come back, I'll need to approach this project differently by partnering with hardware vendors and getting in contact with Rockchip directly (i doubt ill ever get in direct contact because im not a company, im just a random developer). If partnerships don't work out, I'll likely drop support for hardware. This is simply to prevent myself from being overwhelmed and having another public meltdown. I felt obligated to maintain and support over 30 different boards, and honestly, that is an insane amount of work and not maintainable.

[unevoljitelj]

If you ever return to this project maybe its wise to limit yourself to a few chosen boards. Wich boards i cant say bcos i am biased ofc but whatever boards would be chosen those lucky ppl would appreciate it. Your distro is still most wanted. I wish all the best to you whatever you decide to do in the future.

[cscd98]

You've done a fantastic job with this repo, I wouldn't have kept my Orange Pi otherwise. But everyone needs a break now and again to recharge.

Look after yourself

[lukaszsobala]

Your images still serve me well! It would be great if you came back but really, in my experience, there are very few bugs/missing features, at least for RK3588. So maybe it would be a bit easier this time?

[stevepringle]

I think it would be wise to stick to support of the Radxa series of boards (at least initially), as these are the ones that Collabora has been using to develop the mainline Linux support for the rk3588 series of chips.

[hbiyik]

@Joshua-Riek

I have some suggestions

1. It is a great idea to remove any 3rd party driver from the kernel source, and provide them as a prebuilt package (not dkms), i had played with the idea in arch and i think it works, since kernel package is almost the same anytime so the built module works with this single kernel.
   ie: https://github.com/hbiyik/agrrepo/tree/master/kernel/rockchip/linux-aarch64-rockchip-bsp6.1-boogie-openvfd-git

2. it enormously removes a lot of maintenance effort if the dts part of the kernel is completely split to another package. i had even split the branching of the kernel to keep the source tree clean, this way the kernel updates are significantly reduced.

3. the dts files for rockchip boards are not organized correctly, i would think that most of those dts files should be rewritten and abstracted to common parts.