Jump to content

jernej

Members
  • Posts

    1151
  • Joined

  • Last visited

Posts posted by jernej

  1. 1 hour ago, Igor said:

    What about the rest? Analogue and mic support?

    Nope, that goes through AC200 chip and there is no driver for it. Unfortunately it's not easy to reuse BSP driver as the API changed too much. If we would have AC100 driver, this would be easy... I might look into it in future...

    1 hour ago, Igor said:

    I tried few videos over Youtube plugin. Also no UI Kodi sounds ... well. Will investigate further. I will see if it can be brought up on Armbian as well.

    I'll test that a bit later. Anyway, I mostly test using some video files, not with plugins. Note that plugins may have troubles due to recent switch to Python 3 and development version of Kodi.

  2. I don't think any AW board has custom DDR settings. H3 & H5 DDR3 driver currently supports only 1333MHz timings. It would be great to enable per-board settings, but you will have to come up with that yourself. Remember, there is no documentation for DRAM controller, so all that was reverse engineered.

  3. 1 minute ago, JORGETECH said:

    I could ask in Mesa IRC if I can enable it for the Mali T720 MP2 for testing or if it's not implemented yet.

    For T720 you need at least kernel 5.4 and mesa master along with this patch. I'll start testing mesa support for T720 in LibreELEC soon, but according to developer who made T720 mesa PR to LE, it is already quiet good. Hopefully by the time of mesa 20, major bugs will be fixed.

  4. 10 minutes ago, JORGETECH said:

    So in theory the GBM version could be used?

    GBM version is already used in LE, just not for any kind of desktop environment, but for direct rendering.

    11 minutes ago, JORGETECH said:

    Is it possible to use Xorg on top of GBM or do you have to use Wayland (+ xwayland)?

    AFAIK you need X11 version for Xorg, but yes, GBM is needed for Wayland server, whereas wayland version is used by wayland clients. Usually GBM and wayland support are combined into one mali blob, but IIRC, for T720, there are two separate blobs.

  5. @JORGETECH You found Mali T720 fbdev drivers on my github account. I can assure you that they are not Android related. However, using this fbdev driver is very painful on mainline kernel. I guess it's meant to be used with BSP kernel. I had to make one hack in mainline kernel in order to use it, but I don't have patch for that anymore. There is also proper wayland and gbm version for Mali T720, which is hosted on pine64.org wiki. Note that gbm version is successfully used in LibreELEC with mainline kernel. So there is a possibility to use binary driver, it's just that there is no guide how to use it. I would prefer panfrost but unfortunately, support for T720 is in very early stage.

  6. I guess that if you specify only those arguments I gave you to ffmpeg configure script it will build monolithic binaries which is not what you want. I suggest that you check what arguments were used to build ffmpeg from Debian repository by reinstalling it  from repository and running "ffmpeg" without any arguments. Use them and add those which I mentioned. After you build ffmpeg and install it, I think mpv will complain that it can't run with different ffmpeg libraries. Then you have to rebuild mpv.

  7. log status is not implemented by cedrus. Do you have /dev/dri/card0? Do you have any monitor connected? It seems to me that mpv can't find any monitor.

     

    2 hours ago, FGuerzoni said:

    From previous posts I got the fact that the ffmpeg way could decode any h264 profiles. Is it right?

    Yes, it should. But kernel patches used in LE and FFmpeg contain hacks which are used to handle some cases (interlaced videos). That makes interface incompatible for VAAPI library until right approach is agreed upon and implemented. This may take a while, though.

  8. 7 hours ago, FGuerzoni said:

    What is not clear to me is if your patches still use VAAPI.

    I haven't been clear enough. You can go either ffmpeg way or VAAPI way (technically using VAAPI with ffmpeg should be possible, but that's not tested). So no, VAAPI is not used.

     

    Are you running this in desktop environment? If so, it won't work. You have to shut down whatever desktop you're using and run this command from command line. Note that this is only for test to see if known good configuration works.

  9. On 9/17/2019 at 11:08 PM, Lissanro said:

    Armbian with 5.3 worked, except I cannot figure out how to get hardware video decoding (I think 5.3 has some support for H.264 but I could not figure out how to use it, and I prefer to use H.265 if possible).

    It's tricky and needed kernel header files are not exposed in UAPI (userspace API) yet because they are still evolving and changing.

     

    You can try following:

    1. Apply Linux patches 1 (you can filter out only media related patches), 5, 7-11 on kernel 5.3: https://github.com/jernejsk/LibreELEC.tv/tree/cedrus_update/projects/Allwinner/patches/linux

    2. Apply all FFmpeg patches on FFmpeg 4.0.4 (it is easy to port those patches on newer version, to avoid rebuilding mpv): https://github.com/jernejsk/LibreELEC.tv/tree/cedrus_update/packages/multimedia/ffmpeg/patches/v4l2-request-api

    3. Compile FFmpeg with at least following options

    --enable-v4l2-request --enable-libudev --enable-libdrm

    4. Recompile mpv if needed - depends on FFmpeg version used. If it matches to what was was used to compile mpv with, then there is no need.

    5. Add your user to appropriate group ("video" I think) so you can use VPU without root privileges.

     

    Now you should have working mpv with HW accelerated decoding. As I don't use any desktop on SBCs, I run mpv with following options:

    mpv --hwdec=auto --vo=drm video.mkv

    This gives you most speed - HW decoded and directly rendered by DRM driver, so CPU is not involved. Only downside is that it is fullscreen only. Not sure how big performance hit (CPU usage) you would get with X11.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines