jernej

Members
  • Content Count

    909
  • Joined

  • Last visited

2 Followers

About jernej

  • Rank
    Embedded member

Recent Profile Visitors

4282 profile views
  1. jernej

    Mainline VPU

    I don't. As you said, I'm solely focused on decoding. Maybe @Kwiboo knows?
  2. jernej

    Mainline VPU

    That is very much work in progress, so it doesn't work anywhere yet, except basic MPEG4 on Cedrus. I'm not sure if I'll ever finish MPEG4 because it has a ton of variants and even Cortex A7 is capable decoding it. On the other hand, VC-1 has only 3 profiles and it's much more demanding for CPU decoding.
  3. jernej

    Mainline VPU

    You have to make sure that libva-v4l2-request uses same *-ctrl.h files that are in kernel sources under include/media/. For starters, just copy them over from kernel to lib source folder. Then you might need to adjust lib sources to new field names. Unless these files are completely the same, you won't have any success.
  4. A20 has only 2 cores but driver supports up to 4. Perfectly normal.
  5. jernej

    Mainline VPU

    FYI, VAAPI lib is just userspace translation layer between two apis. No kernel hacking needed, apart from applying LE patches.
  6. jernej

    Mainline VPU

    That is the plan. However that can't happen until codecs interfaces in kernel are promoted to stable. That will probably take at least a few more kernel cycles. Nobody wants to screw it up user facing API so everyone is cautious. Actually, not all features are yet supported in kernel, that's also the reason you need kernel patches with experimental improvements. Work on initial vaapi library stalled, but others might take over... Nothing useful at the moment unless you understand both APIs well and you're able to fix it.
  7. jernej

    Mainline VPU

    This can be avoided by using -hwaccel_output_format drm_prime argument. Works good with null output.
  8. Not true. I maintain Allwinner port of LibreELEC and I must say that I'm pleased with H6 multimedia performance. You can try images here. Note that GPU doesn't provide any video decoding. There is VPU for that, but browsers on Linux lag a bit with integration of HW accelerated decoding. On top of that, VPU drivers are wip, so properly put whole video stack together is a bit challenging at the moment. That's why pre-built LibreELEC images exist in the first place.
  9. Simple, LibreELEC heavily patches kernel and ffmpeg for better experience. Patches are slowly getting in kernel but ffmpeg patches will need far more time to be accepted (kernel must first declare this API stable which won't happen anytime soon). You also need Kodi master (e.g. Kodi 19 pre-alpha), because it has a lot of important improvements. Last but not least, only Kodi GBM (e.g no desktop environment) version really works well (zero copy playback) and soon wayland. X11 has no chances to work well. TL;DR: LibreELEC uses features which are in development and not present in any stable version yet. BTW, also 4K HEVC videos work well.
  10. There is no driver for H6 analog codec yet.
  11. Issue is real, so no apology needed. Cable can certainly be a cause for it, but even if it is ok, issue can still happen.
  12. U-Boot is a bootloader, which does low level HW initialization and is responsible for loading Linux and starting it. Sadly, it's not accessible trough file system and no variable will solve this issue. It needs to be re-compiled with display driver disabled and then re-flashed. @Igor how critical is U-Boot display driver? If it is not so critical, I would suggest that CONFIG_VIDEO_DE2 gets disabled for all devices.
  13. Resolution 1024x768 means that kernel was unable to read EDID so it sets default one. This happened now and then on my boards, most frequently with OrangePi PC2. I found out that this problem is solved if display driver in U-Boot is disabled.
  14. @Myy small advice - make links to https://github.com/LibreELEC/LibreELEC.tv because I often delete branches which were already merged. linux56 branch will be removed soon.
  15. No, they are disabled because nobody took time to properly enable them in board DTS until now (it will be in 5.7). No, sun4i-drm is for all Allwinner SoCs, it supports Display Engine 1.0, 2.0 and 3.0. It's just named by Linux tradition where it takes name of first (oldest) supported platform.