<p dir="ltr">On Sep 15, 2016 6:41 AM, "Emil Velikov" <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote:<br>
><br>
> On 15 September 2016 at 10:56, Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote:<br>
> > On 15 September 2016 at 02:54, Ilia Mirkin <<a href="mailto:imirkin@alum.mit.edu">imirkin@alum.mit.edu</a>> wrote:<br>
> >> On Wed, Sep 14, 2016 at 9:52 PM, Ilia Mirkin <<a href="mailto:imirkin@alum.mit.edu">imirkin@alum.mit.edu</a>> wrote:<br>
> >>> Recent changes have been made to the VDPAU state tracker to make it<br>
> >>> unusable with nouveau. Don't provide users with an awfully slow<br>
> >>> "hardware" decoding option.<br>
> >>><br>
> >>> [To preemptively answer the question that will invariably be asked -<br>
> >>> this is due to the state tracker's use of PIPE_BIND_SHARED, which<br>
> >>> nouveau uses to force GART placement to make things with with PRIME.<br>
> >>> However when this is used for output surfaces, which are then blended on<br>
> >>> (the most common way of implementing an OSD), this results in<br>
> >>> *incredibly* slow operation.]<br>
> >>><br>
> >>> Signed-off-by: Ilia Mirkin <<a href="mailto:imirkin@alum.mit.edu">imirkin@alum.mit.edu</a>><br>
> >><br>
> >> Oops, meant to add a CC to mesa-stable, since the breakage was<br>
> >> introduced in 12.0.<br>
> >><br>
> > Just to double-check - by "breakage" and "unusable" you mean that it's<br>
> > "awfully slow" correct ?</p>
<p dir="ltr">Yeah. Nowhere close to able to keep up if blending is enabled, which happens whenever an osd is displayed.</p>
<p dir="ltr">> ><br>
> > Do you/others have any plan to update the state-tracker and/or nouveau<br>
> > to brings things back on par ?</p>
<p dir="ltr">No plans from me.</p>
<p dir="ltr">> ><br>
> Scratch this question - I've just noticed the VDPAU patch which makes<br>
> this one obsolete.</p>
<p dir="ltr">Either this or a "make it work again" patch needs to land.</p>
<p dir="ltr"> -ilia</p>