Re: [Unichrome-users] (EE) VIA(0): Mode not supported by LCD/DFP.

[Luc V. <li...@sk...>]

On Thu, Aug 05, 2004 at 11:18:47PM +0200, Luc Verhaegen wrote:
> On Fri, Aug 06, 2004 at 12:20:52AM +0200, Dennis Bokestig wrote:
> > Sorry.
> > 
> > Regards,
> > Dennis.
> 
> > (II) VIA(0): ViaGetNearestRefresh: preferred: 75
> > (II) VIA(0): ViaGetNearestRefresh: Refresh: 75 (index: 1)
> ...
> > (II) VIA(0): VIAGetPanelInfo
> > (--) VIA(0): VIAEnableLCD
> > (II) VIA(0): VIAGetPanelSizeFromDDCv1
> > (II) VIA(0): I2C device "I2C bus 2:ddc2" registered at address 0xA0.
> > (II) VIA(0): I2C device "I2C bus 2:ddc2" removed.
> > (II) VIA(0): Manufacturer: AUO  Model: e12  Serial#: 1298
> > (II) VIA(0): Year: 2004  Week: 2
> > (II) VIA(0): EDID Version: 1.3
> > (II) VIA(0): Digital Display Input
> > (II) VIA(0): Max H-Image Size [cm]: horiz.: 29  vert.: 22
> > (II) VIA(0): Gamma: 2.20
> > (II) VIA(0): No DPMS capabilities specified; RGB/Color Display
> > (II) VIA(0): First detailed timing is preferred mode
> > (II) VIA(0): redX: 0.579 redY: 0.340   greenX: 0.310 greenY: 0.550
> > (II) VIA(0): blueX: 0.154 blueY: 0.154   whiteX: 0.314 whiteY: 0.329
> > (II) VIA(0): Manufacturer's mask: 0
> > (II) VIA(0): Supported additional Video Mode:
> > (II) VIA(0): clock: 65.0 MHz   Image Size:  286 x 214 mm
> > (II) VIA(0): h_active: 1024  h_sync: 1048  h_sync_end 1184 h_blank_end 1344 h_border: 0
> > (II) VIA(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 806 v_border: 0
> > (II) VIA(0): Monitor name: Color LCD
> > (II) VIA(0): VIAGetPanelSizeFromDDCv1: 0
> 
> Right, i saw a bug there, the GetNearestRefresh routine resorted to 
> 60Hz, seems fixed now. I had overlooked it in my own testing, looking
> back it was present there too.
> 
> And then we have the full and complete DDC information of your panel. 
> >From which, it seems, X is unable to retrieve the information it needs.
> Therefor, it returns the size at its default, being 0, but it claims to 
> have gotten information anyway, and thus bypasses everything else. So it
> results in invalid once again. Anyway, we've come quite a bit closer, 
> even though we haven't fixed it yet.
> 
> I'm now going to try to find out why X failed to parse this.
> 
Ok, it was not X that failed to parse this, it was the via driver 
itself.

I've now written a small routine which should also check the other part 
of the EDID information.

Apply this patch ontop of clean CVS.

Luc Verhaegen.