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

[Jesse Barnes]

On Thu, 28 Oct 2010 18:47:09 +0300
Pauli Nieminen <ext-pauli.nieminen at nokia.com> wrote:
> > Most of what you have in (b) is pretty straightfoward; even the shared
> > drawable case shouldn't be too bad, since each X connection could have
> > bits indicating whether the counter has been picked up after a CRTC
> > move.
> 
> 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.

Yeah that would be a good extension though; we may as well expose the
fact that different display pipes exist on the system, and have
corresponding MSCs.  Old applications using SGI_video_sync or existing
OML behavior would work like they do today (with an MSC value that may
jump, which we could fix with the virtualize count), and new ones would
be pipe aware.

-- 
Jesse Barnes, Intel Open Source Technology Center