• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by jernej

  1. To enable HDMI in U-Boot for any A64 board you have to first enable DE2 driver in config file and then somehow enable voltage regulator responsible for HDMI power (this is main reason why it's not currently supported). U-Boot doesn't have AXP803 driver. Probably easiest way would be to modify ATF.
  2. Given than GPU DVFS is not in mainline yet, I think best solution would be to remove those patches from Armbian build system and maybe add a patch which would increase frequency and adjust voltage...
  3. GPU, Display Engine and HDMI all have different clock sources. It could still be HDMI clock issue, just different...
  4. In the past, I tested @Clément Peron's patches on Tanix TX6 which has fixed GPU regulator and it has same problem. I'm pretty sure at this point that it's clock driver issue.
  5. Well, kernel modification is needed for better decoding (less glitches). Probably new *-ctrl.h files contain new fields (not 100% sure) which also need to be filled. There is no any post processing implemented here like scaling. It would be possible to do that via SoC specific peripherals but that wouldn't be universal and thus it's out of scope of this library. Anyway, I'm glad you succeeded.
  6. Sorry, no. I never worked with AC108, 3.10 kernel or Android on Allwinner boards. Just mainline kernel (currently 5.7), proper Linux (no Android) and only codec I have experience with is DW-HDMI for audio over HDMI.
  7. I don't know if that will work. LibreELEC uses latest versions of all libraries while Armbian not necessarily. Also be aware that Kodi in LibreELEC is meant to be run without X11 which means you have to drop into console first and then run Kodi.
  8. You could but video playback will be still painful. While audio interface is pretty standardized these days, video decoding is only getting there. Apps don't support video decoding on A20 yet, unless they are patched too. There is translation layer for VAAPI in works, but I'm not sure if it is useable in current state. LibreELEC serves as testing bed for video playback on Allwinner SoCs (at least for me) and environment is highly controlled to offer best experience possible. This means that playback is done through patched ffmpeg for video decoding and Kodi uses a render method not many apps use (DRM planes) and that only works well with full screen apps (GPU is not used at all).
  9. @Zoom yes, but download link is preferable
  10. @Zoom do you have Android image or update file for your TX6a variant? I would like to extract DTB file from it.
  11. I wouldn't be so sure. However I never researched it so I won't make any claims here.
  12. You shouldn't unload I2C driver because power regulator (PMIC) is controlled over it. With I2C driver unloading you effectively disable power regulation.
  13. A bit of HW details. H3 and most of AW SoCs for that matter have RTC integrated in which can be clocked from internal or external clock. Internal clock is sadly inaccurate, so it's borderline useable for keeping time, but some boards, like NanoPi NEO still omit external clock (price consideration, I guess). So, main issue about RTC to keep time is if it has separate power supply which is still enabled when main power supply is disconnected. On schematic, this is VCC_RTC. As you can see on NanoPi NEO schematic, RTC and main power supply are connected together, so RTC will lost power and with that time every time main power supply is disconnected.
  14. Mali is only for rendering, video decoding is done on separate HW core. However, its driver is not finished, VAAPI lib for it is also not finished yet and most of all, firefox supports HW video decoding (e.g. VAAPI) only on wayland. So, nothing that you could use right now. If you want decent video player on OPi Plus2E you can use LibreELEC image (Kodi) which has all work in progress included, but that is probably not something you had in mind (multimedia center app with no browser but youtube addon can be installed).
  15. jernej

    Mainline VPU

    I don't. As you said, I'm solely focused on decoding. Maybe @Kwiboo knows?
  16. 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.
  17. 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.
  18. A20 has only 2 cores but driver supports up to 4. Perfectly normal.
  19. jernej

    Mainline VPU

    FYI, VAAPI lib is just userspace translation layer between two apis. No kernel hacking needed, apart from applying LE patches.
  20. 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.
  21. jernej

    Mainline VPU

    This can be avoided by using -hwaccel_output_format drm_prime argument. Works good with null output.
  22. 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.
  23. 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.
  24. 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.