Jakob Bornecrantz wrote: > Hi Chia-I and Luca > > you guys are doing great work with the EGL state tracker. So I thought > it would be a good time to open up a discussion about the way that the > API state trackers talk to the EGL, dri and other co state trackers. > > I have attached a proposed interface to be used between the different > state trackers. I know that Chia-I and I have talked about it before > and nothing much have changed since then. The main point of this API > is to eliminate the last references to winsys in the gallium > interface, This could be done by just moving update_buffer/ > flush_frontbuffer to pipe_screen, but this is not acceptable, since > the pipe driver is not the one to take care of those things. > > Some things that needs to worked out about this interface is how to > handle glViewport vs DRI2, since the code in glViewport needs to force > a update of the buffers in DRI2 but not for other state trackers. If > we can some how work around the need to force a update in a way that > works on old servers that would be great, but I doubt that can be done. >
Don't we also ideally need to catch glReadBuffer / glDrawBuffer calls and forward them to the DRI state tracker to know whether to request a frontbuffer or not in double-buffered mode? /Thomas ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
