EGL_MESA_screen_surface proposal

Benjamin Herrenschmidt benh at kernel.crashing.org
Wed Mar 16 17:59:25 PST 2005


On Wed, 2005-03-16 at 20:51 -0500, 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.

Ugh ? Setting a mode includes setting a depth imho (depth has impact on
various bits of the mode setting process at the driver level), so those
2 things should go together, and there are more failure cases than just
exceeding bandwith when setting the depth.




More information about the dri-egl mailing list