EGL_MESA_screen_surface proposal

[Brian Paul]

Jon Smirl wrote:
> On Thu, 17 Mar 2005 12:29:16 +1100, Benjamin Herrenschmidt
> <benh at kernel.crashing.org> wrote:
> 
>>I wouldn't do something as complex I suppose for EGL, but I would at
>>least put clearly in the spec that doing a mode setting may not result
>>in that actual mode beeing reallly set. That is the user is expected to
>>re-query for the mode after setting it. The driver may have had to do
>>something else at the last minute due to whatever internal problem,
>>error, out of resource, etc...
> 
> 
> I would flip this around. The modes can always be set. What fails it
> attaching a surface to the mode. It's the surface that carries the
> depth information and causes the bandwidth to be exceeded.
> 
> It might be worth looking at a model where mode and surface setting is
> combined.

I'm leaning toward a model with depth is not part of the mode 
information and setting the screen's surface and mode are done with a 
single function.

I've just finished updating the spec in this manner and have added a 
number of other items.  I'll post it soon.


 > Or mode sets are not applied until a surface set follows. I
> don't like the transactional hole of setting the mode while still
> using the old surface.

Me either.

-Brian