LaCie 321 DFP: mode misdetected - EDID misinterpreted?

[Alex Deucher]

On 6/14/07, Mourad De Clerck <mourad at aquazul.com> wrote:
> On 14/06/07 21:14, Roland Scheidegger wrote:
> > Mourad De Clerck wrote:
> >> I've got 2 LaCie 321 DFPs, but can't seem to drive them at the native
> >> resolution (1600x1200) with the open "nv" driver. The maximum resolution
> >> I'm able to use is 1280x1024.
> >
> > This rather looks to me like your panel lies about its size, I don't
> > think there is any "misinterpretation".
> > Maybe the driver could be made more intelligent and just
> > ignore it if the panel provides a prefered detailed timing with a larger
> > resolution (which is probably what the nvidia driver does).
>
> That's rather annoying. From what you're saying I'm assuming that the
> logic to determine the "right" mode is driver-specific at the moment;
> Will this be different with RandR 1.2?

If you still have the radeon, I'd be interested in knowing how it
performed with the randr-1.2 branch.  The crtc and output handling has
changed significantly.  With nv, I think the driver relies on the bios
for much of the output setup, so that may be part of the problem.

>
> > This is certainly not the first monitor with bogus edid data.
>
> Would it be possible or worth it to have a "quirks" list with monitors
> that need "corrected" (read: faked) EDID data?
>

If the monitor indeed has a bad edid data, we can add a quirk once we
find out what quirk it needs.

Alex