Display MoreI would like to understand the differences :
test builds from kwiboo with his newest developments for RK Hardware ?
automatically generated LE builds
may have newest Kodi changes but kwiboos developments only if someone from LE team has merged them after request ?
Did I get this right ?
Is the same kernel used for the rockchip builds?
Hi
Maybe this can help.
LibreELEC uses the following RK kernel code
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
Kwiboo's build's use the following RK kernel code.
LibreELEC.tv/package.mk at rockchip-part6 · Kwiboo/LibreELEC.tv · GitHub
You then search for that specific commit in the kernel here - GitHub - rockchip-linux/kernel: BSP kernel source
LibreELEC - eae92ae2b930999857df47c3057327c1c490454b - All changes up to 05 Feb 2018
media: rockchip: rga: add userptr to use normal cache-enabled memory
Kwiboo - b8154f1fba5496be524fb110c78ffe49ec58d3f1 - All changes up to 25 days ago, 4 June 2018.
Revert "arm64 Kconfig: Move LIST to a safe value"
So this uses about 4 months later commits and code updates.
All the changes up to that commit will then be used by LibreELEC for the kernel, newer commits(changes) past that are ignored.
Think of a book(RK kernel), LibreELEC's bookmark is at eg. page 45 and Kwiboo's at page 95 and the book has 130 pages.
Then you can do the same and compare for
rkmpp - the video codecs
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
Kodi package - LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
(search at 'http://github.com/xbmc/xbmc')
Kodi package is usually updated once or twice a month by LibreELEC.
and all the other packages
All these RK changes still need to be merged into LibreELEC and is not yet part of the nightly test builds.
Kwiboo has even more wip commits that are not even added there yet.