EGL_MESA_screen_surface proposal

[Alex Deucher]

On Wed, 16 Mar 2005 14:51:37 -0500, Jon Smirl <jonsmirl at gmail.com> wrote:
> On Wed, 16 Mar 2005 12:45:09 -0700, Brian Paul
> <brian.paul at tungstengraphics.com> wrote:
> > > The only reason you need the interlace attribute is when you have both
> > > 1080p and 1080i available and you want to force 1080i. But now that
> > > think about it I don't think you'll ever want to do this so we don't
> > > need the attribute. I can't think of a situation where you want to
> > > force an inferior mode when you have a better one available.
> >
> > Suppose I'm a video engineer and I just want to test interlaced mode
> > with my lab equipment.
> 
> Then you'll know enough to go edit external config files to suppress
> the reporting of the progressive modes and make the interlaced one
> visible. Framebuffer has a mechanism to add/delete modes as reported
> by DDC. Just delete the progressive one that is obscuring the
> interlaced one and restart XGL.

It'd be preferable to switch between the two with requiring a restart.

> 
> >
> > If a graphics card supports 332RGB TrueColor mode few people may ever
> > want to use it since 888RGB is so much nicer, but the option to use it
> > should still be there.
> 
> Color depth is a function of the surface, not the mode.
> 
> --
> Jon Smirl
> jonsmirl at gmail.com