ion supported is 3.0 or greater ? Is there an assumption that all
> > dri2/3 modules support it ?
>
> [Zhang, Xiong Y] the patch lack of checking of OpenGL version >= 3.0, I will
> add it.
[Zhang, Xiong Y] Since GL version is determined by dri drivers like i965,
swrast, how could I ge
or greater.
> >
> > So when both and are None, it could pass NULL drawable
> > into driver instead of returing GLXBadDrawable.
> >
> I'm a bit fresh in the area, but where do we check that the OpenGL version
> supported is 3.0 or greater ? Is there an assumptio
> Le 24/03/2015 06:50, Zhang, Xiong Y a écrit :
> >> You seem to miss the case when one is None and not the other.
> >> It should return BadDrawable too.
> >>
> >> This particular case seems not handled by the dri2 code either, and
> >> the gallium
> You seem to miss the case when one is None and not the other.
> It should return BadDrawable too.
>
> This particular case seems not handled by the dri2 code either, and the
> gallium
> state tracker seems to handle it in bindContext, but not the intel code for
> example.
hi, Kristian:
This patch block the startup of desktop-shell client in weston.
Panel surface and background surface share a common context.
First when client redraw panel surface, _mesa_make_current will set
brw->ctx.ViewportInitialized to true.
Later when client redraw background surface
Using the latest mesa master tree, I test it on my Core i7-2600 :
1) In default configuration, the monitor's refresh rate is 60FPS, so the test
result is 59.3 FPS
2) export vblank_mode = 0, then the test result is 170 FPS.
I don't see the big difference between using direct transfer or using P
