On Thu, 28 Jul 2022 at 15:04, Anton Khirnov wrote:
>
> Quoting Emil Velikov (2022-07-22 15:27:26)
> >
> > Assuming I'm reading the code correctly, currently when both are
> > undefined vaapi_device_create() will be basically a dummy, doing some
> > basic malloc + opts parsing and erroring out.
> >
Quoting Emil Velikov (2022-07-22 15:27:26)
>
> Assuming I'm reading the code correctly, currently when both are
> undefined vaapi_device_create() will be basically a dummy, doing some
> basic malloc + opts parsing and erroring out.
>
> So as-is functions like av_hwdevice_ctx_alloc() will return s
On Thu, 21 Jul 2022 at 22:06, Mark Thompson wrote:
>
> On 20/07/2022 11:56, Emil Velikov wrote:
> > From: Emil Velikov
> >
> > Similar to the VAAPI_X11 bits, guard all the VAAPI_DRM parts behind a
> > compiler guard.
> >
> > Signed-off-by: Emil Velikov
> > ---
> > libavutil/hwcontext_vaapi.c |
On 20/07/2022 11:56, Emil Velikov wrote:
From: Emil Velikov
Similar to the VAAPI_X11 bits, guard all the VAAPI_DRM parts behind a
compiler guard.
Signed-off-by: Emil Velikov
---
libavutil/hwcontext_vaapi.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libavutil/hwcontext_
