Is OMX_IndexConfigBufferStall parameter available in mmal? I need to access it, but my video_decode is created and handled using mmal.

Thanks,
Alessandro

No, it's not mapped. TBH I'd never even heard of it.
I'm doing some other firmware changes, so I'll add the mapping.

Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

I found it here: https://github.com/raspberrypi/firmware ... ecode.html
Also could be useful OMX_IndexParamBrcmSetCodecPerformanceMonitoring to be available in mmal.
Thanks, for your work!

OMX_IndexParamBrcmSetCodecPerformanceMonitoring isn't sensible.
From the docs:

OMX_IndexParamBrcmSetCodecPerformanceMonitoring: 131
Configures a codec so that it outputs performance statistics to
the given DECODE_PROGRESS_REPORT_T structure (passed as a pointer).
This structure can then be read by the client to find out where the codec is
at in its processing.

That pointer is a VideoCore pointer, not ARM. There's no easy way to generate such a pointer and map it into ARM memory space. I don't believe there's any documentation published over the format of the structure either.

Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.