EGL_MESA_screen_surface version 5

[Jon Smirl]

On Apr 7, 2005 11:05 AM, Adam Jackson <ajax at nwnk.net> wrote:
> > > in the kernel. It is then up to the higher layers to catch the event.
> > > fbdev may also blank the monitor until a new mode is set. This is to
> > > prevent the old mode from destroying a new monitor.
> >
> > Would this HAL event be a signal or interupt or what?
> 
> HAL events are generally multicast over DBUS to any interested listening
> application.  The driver could in principle open a new fd for this, but it
> would be more straightforward for us if the event were also noted in the
> sarea.

Doesn't this have to be processed at the highest level? We can't
change the format of the framebuffer without letting the app drawing
the desktop know. Instead the app drawing the desktop catches the
event,  picks a new format and sets it into EGL.

-- 
Jon Smirl
jonsmirl at gmail.com