Re: [Mesa-dev] [PATCH v3] st/va: delay decoder creation until max_references is known

2015-11-30 Thread Julien Isorce
On 30 November 2015 at 12:03, Emil Velikov wrote: > On 26 November 2015 at 08:45, Julien Isorce > wrote: > > > --- a/src/gallium/state_trackers/va/picture.c > > +++ b/src/gallium/state_trackers/va/picture.c > > > @@ -113,12 +118,37 @@

Re: [Mesa-dev] [PATCH v3] st/va: delay decoder creation until max_references is known

2015-11-30 Thread Christian König
On 26.11.2015 09:45, Julien Isorce wrote: In general max_references cannot be based on num_render_targets. This patch allows to allocate buffers with an accurate size. I.e. no more than necessary. For other codecs it is a fixed value 2. This is similar behaviour as vaapi/vdpau-driver. For now

Re: [Mesa-dev] [PATCH v3] st/va: delay decoder creation until max_references is known

2015-11-30 Thread Emil Velikov
On 26 November 2015 at 08:45, Julien Isorce wrote: > --- a/src/gallium/state_trackers/va/picture.c > +++ b/src/gallium/state_trackers/va/picture.c > @@ -113,12 +118,37 @@ handlePictureParameterBuffer(vlVaDriver *drv, > vlVaContext *context, vlVaBuffer * > default:

[Mesa-dev] [PATCH v3] st/va: delay decoder creation until max_references is known

2015-11-26 Thread Julien Isorce
In general max_references cannot be based on num_render_targets. This patch allows to allocate buffers with an accurate size. I.e. no more than necessary. For other codecs it is a fixed value 2. This is similar behaviour as vaapi/vdpau-driver. For now HEVC case defaults to num_render_targets as