10-08-2017, 02:22 PM
(This post was last modified: 10-08-2017, 03:11 PM by stuartiannaylor.)
(10-08-2017, 07:34 AM)Kwiboo Wrote:(10-08-2017, 05:09 AM)zarusz Wrote: Now, I am a bit confused by having the two LibreELEC releases - provided by you and Raybuntu. Looks like your linux-rockchip work is incorporated in the Raybuntu distro.
Which one do you suggest I go with?
I would recommend you to try both depending on what you need, my image is rather plain LibreELEC with Rockchip support and only have some of the add-ons available (currently has a newer kernel version).
It was originally intended as a proof-of-concept and testing image, and will probably only get one more update after LibreELEC 8.2 / Kodi 17.5 is released and I have completed NL-PCM/HBR audio support. After that my focus will be on upstreaming.
Raybuntu's image is using 32-bit user space and should work with widevine and probably have more add-ons available.
To be honest I am really confused and perplexed by the choice from Rockchip and here with the Pine & community builds.
Rockchip seem to be aiming at Stretch with a 4.4 kernel which upporting a kernel is a new one for me and I am trying to get my head around it.
Then we have the Pine Jessie LXDE where at least the 4.4 kernel is a backport, which is the same with the Xenial community builds in that respect but the slight deviation from Debian to a Buntu.
Then we have community Stretch & Artful and various desktop versions based upon these with some libreelec hacks from Raybuntu & Kwiboo.
In every image theOpenGL ES and EGL core for the RK3328 that rockchip are developing is missing and a relatively small community is spread to the winds and seems to be having little input on the Rockchip opensource initiatives.
You just have to look at there github repo's to see the lack of input which would just seem strange with an aversion to Rockchip?!
What Ayufan is doing is great as apart from supplying an image there is a huge amount of documentation and its only the quantity that I am struggling with.
Pine to be honest I am wondering what they are doing https://github.com/rock64-linux
It just seems strange we don't have a singular reference core that brings in up to date https://github.com/rockchip-linux and that these seem to be feeding back to that core.?
I found another recent repo https://github.com/mth/xf86-video-armsoc which has limited framebuffer support but the more I read the more confused I get on which way X is going to be implemented in at least a first working mode.
There are probably all good reasons for this, but yeah I am confused as hell and even struggling to work out an approach.
Seems to be a plethora of talent all going separate ways and not a singular half working Xserver unless its some horrid llvmpipe virtual cpu server.
Prob if you can implement the framebuffer driver then xserver will gain some egl support for Krypton.
https://github.com/mth/debian-ffmpeg-rkmpp
I am still scratching my head to why no-one seems to be using the custom rockchip xserver?