This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/AM3352: Compiling ffmpeg with hwaccel

Part Number: AM3352

Tool/software: Linux

Hi,

I'm trying to improve performance when recording videos by enabling hwaccel to the ffmpeg config options. Thing is, I'm not sure if I need to do anything else besides enabling the Graphics Support options in the kernel. I took a look at  the Graphics SDK Quick installation and user guide, but Im' not sure if this will help me. All I want is to use the graphics processor to ease the load on the CPU.

Regards,

Guilherme

  • Hi Guilerme,

    I'm trying to improve performance when recording videos by enabling hwaccel to the ffmpeg config options. Thing is, I'm not sure if I need to do anything else besides enabling the Graphics Support options in the kernel

    You're correct, you need to enable the GPU & load the pvr driver in the kernel. This should be enough to offload the CPU.

    Best Regards,
    Yordan
  • Yordan,

    I followed the instructions to install the Graphics SDK, and managed to generate the drivers for my board. However, when I run the install script, it is not able to initialize pvrsrvctl, producing the following output: /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=4). The pvrsrvkm module loads just fine, but the omaplfb one doesn't load. Could this be a problem?

    Attaching strace to the prvsrvctl process, it seems that it cannot open the prvsrvkm device:
    PVR:(Error): OpenServices: Cannot open device driver /dev/pvrsrvkm. [79, /pvr_bridge_u.c]
    PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [2413, /bridged_pvr_glue.c]
    PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [37, /srvinit.c]
    /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=4)

    I checked around and it seems that I would need to use PM_RUNTIME=1 for the AM335x, if it has the hwmod patch (which it does). However, this is the default value for the newest SDK.

    What could be causing this?