[PATCH 2/2] DRI2: Add error message when working around driver bug

Pauli Nieminen ext-pauli.nieminen at nokia.com
Thu Oct 28 09:34:05 PDT 2010


On 28/10/10 18:06 +0200, Ville Syrjälä wrote:
> On Thu, Oct 28, 2010 at 05:47:09PM +0200, ext Pauli Nieminen wrote:
> > One option would be adding crct id parameter to calls.
> > 
> > glXGetMscBaseRateOML would return rate, base msc and pipe id where this msc
> > value is valid. Now all MSC calls would take the returned pipe id as
> > parameter. If pipe id doesn't match current crtc any more then call would
> > fail.
> > 
> > This would allow complex applications to pass same pipe id to different
> > context.
> > 
> > Negative side is that API would have to be changed to include extra
> > parameter.
> 
> And what about cases involving multiple CRTCs? Would the user just
> choose one? And what about the other CRTCs then, could some suffer from
> tearing or should more buffers be added to the mix to allow the CRTCs
> to scan out of different buffers and flip at their own rate?
> 

But for common case it should be enough to use N-buffering for good
performance and fairly good timing. Driver can do fairly good decision when
flip should happen for each CRTCs.

Some clients might want to be aware of mirrored or extended rendering target.
But that can be exposed in separate extension.

Pauli



More information about the xorg-devel mailing list