fbdev egl driver passes glitx rendertest

[Matthias Hopf]

> 1. Single/Double-buffered surfaces
> 
>    Create EGL_MESA_single_buffer extension to define new
>    EGL_SINGLE_BUFFER_MESA token/attribute for EGLConfigs to
>    allow creating single-buffered surfaces.

It could be worth the effort to add this to the current extension. A
display does not have to support this, if no single- (or no double-)
buffered surface are implemented, they just don't have to be exported as
valid modes. That way implementors could decide to support
single-buffered mode first, and add double buffering later.

Just my two cents, though.

> 4. RGB vs. color-index modes:
> 
>    Is there an immediate need to support color index (i.e.
>    PseudoColor) modes?  If we do need color index, we'd need an
>    EGL_COLOR_INDEX_MESA token for EGLConfigs and a set of functions
>    for loading/getting/managing color palettes.  Maybe other things.

Color indexed modes are not accelerated by all modern graphics hardware
known to me. There had been rudminentary support on old SGI machines,
but not on nowadays hardware -> kick it.

> 5. TrueColor vs. DirectColor:
> 
>    For now, perhaps just treat DirectColor visuals as TrueColor;
>    initialize the lookup tables to linear ramps.  If we'd fully
>    expose DirectColor modes, we'd again need some color palette
>    functions.

We should have the possibility to specify color ramps in a seperate
extension, regardless of the visual type (monitor gamma always has to be
compensated). That effectively removes the need for directly supporting
DirectColor type visuals.

Matthias

-- 
Matthias Hopf <mhopf at suse.de>       __        __   __
Maxfeldstr. 5 / 90409 Nuernberg    (_   | |  (_   |__         mat at mshopf.de
Phone +49-911-74053-715            __)  |_|  __)  |__  labs   www.mshopf.de