> > It might be possible to set up X11 to avoid the overscan area. > > Have to give that some thought. > > > > For non-X11 applications, (and even for X11 if it turns out to > > be non-trivial to avoid the overscan area) it would be handy if > > there was a way for the software mode and the actual hardware mode > > to be different. The software would see fewer pixels so that it > > wouldn't paint things in the overscan area. > > > > Given the limited resolution of standard resolution TVs, it > > would be good to let the user fine tune the software mode > > to match the actual overscan of their particular TV. > > > > Hmmm... This is basically just a different application of the > > same capability in my previous posting. (Allowing the firmware > > to talk at 640x480 and a fixed-frequency monitor to receive say > > 1280x1024.) > > > In modesetter terms, there is a difference between overscan and > blanking. Overscan is where the CRTC is not blanking, but where it > isn't pumping out pixels either.
We are talking about the overscan on television sets, where the deflection is cranked up so high that part of the picture is behind the bezel and thus not visible. If you display X11 on a TV, there might be important things hiding behind the bezel. Even with a TV show, if it is tightly cropped and the TV set has a lot of overscan it can hide something important. Computer monitors normally have underscan. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
