guybrushthreepwood

I created Kodi packages for v4l2-request, tested on Orange Pi+2e (Allwinner H3) running Armbian Bullseye with the current 5.10.y kernel.
 
So far, HW video playing works fine with MPEG2 and h.264 up to 1080p. Kernel patches are needed to improve resolution and codec support. GUI performance is just enough, but it can probably be also improved with kernel patches.
 
So the userspace part is now working, the kernel improvements remain in the TO-DO list.
 
Packages can be found here: https://users.armbian.com/jmcc/packages/kodi-mainline/
 
These should still be considered WIP, although fully functional already. Instructions:
Download the packages for your architecture, and install them with "dpkg -i". Only kodi-mainline and kodi-mainline-bin are essential, the others are optional. Run "apt -f install" Make sure there is no X server running, and start kodi from console typing "kodi" @balbes150 you may be interested in this. They should also work in Rockchip, but I haven't tested yet.

Attached is jernej's patch, slightly modified to work with 5.10.13, sorry for posting it here. The overscan issue can be fixed with this tool, https://projects.nwrk.biz/projects/allwinner-tvout/wiki, this was described in this forum but I don't have the link. The washed out (hardware) issue has also been described here and can be easily fixed with a resistor. There are also DRM properties for dealing with TV offsets and sizing issues but I have not figured out where to put them in the user level device tree, does anyone know? (I tried put them under the tve node but didn't work.) The properties are described here: https://www.kernel.org/doc/html/v4.12/gpu/drm-kms.html?highlight=drm tv#existing-kms-properties
zzzz-tv-cvbs.patch
 
Patch was tested to work with zero, and neo...

Yes, meson uses stateful whereas Cedrus and rkvdec use stateless (request api).
Actually only one really worked on this driver but stopped working on most (all?) things due to real-life issues.
Vanilla Kodi will work for video decoding, but if you want HW deinterlacing, that will need Kodi patch and additional one for ffmpeg.

I apologize. Yes, jernej hasn't actually said what I've instead said but just that there is a lot of work (optimizations) to do. I've said it my way which is the wrong way because linked with my very very limited knowledge, not Armbian fault nor its developers. You're absolutely right and I can only apologize.

The build script, after git checking out the kernel sources, will apply the patches. All of the applied patches will appear in order, with a green indicator when they are applied OK and yellow or red when there is some problem. Though, since the text moves so fast, you probably didn't notice it.
 
The easiest way to check how the patches are applied is to add the option CREATE_PATCHES=yes to compile.sh. It will make the script pause twice, first after applying the u-boot patches and then after the kernel patches. You can see if your patch was applied correctly, and troubleshoot if not.
 
Simply open the commit in GitHub, and then at the address bar add ".patch" at the end.

A little more detailed explanation about CREATE_PATCHES: https://zuckerbude.org/armbian-using-create-patches/

What? Why don't you use the Armbian Build Script? That is what all this project is about! 
 
Applying a patch is as easy as putting it on the corresponding folder under "userpatches", or either use the command line option "CREATE_PATCHES=yes" in case you want to apply it manually.