[Openchrome-users] VIA VT1631 LVDS Transmitter ??

[Jeremy C. Reed]

On Tue, 16 May 2006, Jeremy C. Reed wrote:

> > > When using vesa or openchrome's via with VBEModes, it appears there is not
> > > any antialiasing.
> > >
> > ?
> 
> > you're getting font anti-aliasing when using the monitor out? but not 
> > with the LCD panel?
> 
> Note that the LCD panel does not work with "via" without VBEModes. The LCD 
> panel does work with "via" with VBEModes true or when using "vesa".
> 
> > not that I don't believe you. :) but it might be interesting grabbing a 
> > screenshot of the two and seeing if anything "leaps out".
> 
> I also don't see it myself -- but just am speaking with two admins of the 
> box that see the differences with their eyes when switching between "vesa" 
> and "via".
> 
> I will get some screenshots...

I have some screenshots that I can make available via http://.

First we used both xwd and gnome's screen capture utility. But the  
screenshots from these showed great antialiasing. I was told that the text 
on the screen was all jagged but the screenshots looked good.

So the owner used a camera and took pictures. When using "via" on his VGA 
monitor, the antialiasing looked good. But when using "via" with VBEModes 
(so it would display on the LVDS) on the LCD panel and on the VGA monitor, 
the pictures are bad -- text is all jagged.

Why would a screenshot (using xwd) show nice antialiasing, when the real 
screen is showing jagged text?

And how can we get the real displays (especially LVDS) to show the nice 
antialiasing?

The same problem is when using "vesa" driver instead of "via". "via" 
has good antialiasing but doesn't power the LVDS. "vesa" does power the 
LVDS but has no antialiasing.

Thanks!

 Jeremy C. Reed