In order to reduce the number of images, I trimed to build only the most basic version which allows to boot all revsions and has all capabilities we need. (People can replace dtb from /usr/share/bootloader)
I also dropped some boards where I found shortcomings in the device tree which might be easy to solve but I can't test and they were not supported in earlier releases.
This adds a mapping for device trees which differ between vendor and mainline kernel and will therefore allow updates to new releases.
The old ones will be replaced by the new, or at least most appropriate (in case of RK3328 box devices), devicetrees in mainline kernel.
Besides a warning will be shown now if the device tree that the installation uses does not exist in the update tarball.
MiQi and Tinker devices have been merged to RK3288 device at some point after LE9.2 release.
This allows updating for them as well through mapping to the new RK3288 device.
While at that also drop the pointless check for kernel versions.
The default of 512k is too small at 192kHz/8ch, kodi can only get a
86ms buffer instead of the 200ms buffer it usually wants. That results
in occasional buffer underruns when playing media from local storage
which is uncached in kodi's default settings.
Increase the alsa buffer size to 1.2MB so kodi can get the audio buffer
size it likes to have.
Signed-off-by: Matthias Reichl <hias@horus.com>
samsung-0001-FROMLIST-v1-serial-samsung-Re-factors-UART-IRQ-resou.patch
- deleted
- ref: https://www.spinics.net/lists/linux-serial/msg39463.html
samsung-0012-MEMEKA-phy-exynos5-usbdrd-Calibrating-makes-sense-on.patch
- deleted
- incorporated in 5.10.y
samsung-0013-MEMEKA-clk-samsung-exynos5420-Keep-top-G3D-clocks-en.patch
- deleted
- replaced by 67f96ff7c8
- included in kernel 5.10.y
samsung-0016-MEMEKA-thermal-add-irq-mode-configuration-for-trip-p.patch
- updated for 5.10.y, needs to be build/run tested.
Now that we have PCIE support for RK3399 we can also add support for
same PCIE wifi chipsets - this also adds some firmware to RK3399 images
which is required by some of them.
I wrote the driver some month ago and have been testing it on everday
basis since then (by just using it). I will have to add some more
functionality before upstreaming it, since the IP supports way more
then just deinterlacing - however: thats the only use-case for kodi now.
The current rkvdec HEVC code can be taken as-is, I only had to add some
seperation for the versions to ensure it won't be taken for H264/VP9 on RK3288.
