Re: [PATCH] drm: Add EDID_QUIRK_FORCE_REDUCED_BLANKING for ASUS VW222S

[Florian Mickler <florian@mickler.org>]

Dear Paul,

do you have a quick pointer to your decoded EDID? Maybe we can tell the
VW222S and the VW222U apart. Then a small hack to the quirk-code should
do the trick.

Else, I'm afraid the right thing to do is to revert the quirk.

I will provide the log files as soon as I'm back with that monitor,
which should be next year... (Means tomorrow or the day after)

Regards,
Flo

On Mon, 31 Dec 2012 17:37:24 +0100
Paul Menzel <paulepanter@users.sourceforge.net> wrote:

> Dear Florian,
> 
> 
> Am Freitag, den 21.12.2012, 14:52 +0100 schrieb Florian Mickler:
> > On Tue, 18 Dec 2012 23:33:20 +0100
> > Paul Menzel <paulepanter@users.sourceforge.net> wrote:
> 
> > > Am Dienstag, den 18.12.2012, 21:03 +0100 schrieb Florian Mickler:
> > > 
> > > > On Wed, 15 Aug 2012 17:40:40 +0200 Paul Menzel wrote:
> > > > 
> > > > > Date: Wed, 8 Aug 2012 23:12:19 +0200
> > > > > 
> > > > > Connecting an ASUS VW222S [1] over VGA a garbled screen is shown with
> > > > > vertical stripes in the top half.
> > > > 
> > > > This patch, which was merged in v3.6-rc4, makes the image on my ASUS
> > > > VW222U ca. 1 inch too wide left/right and top/bottom.  The effect is as
> > > > if the image was zoomed (bigger, more pixely).
> > > > 
> > > > Reverting it fixes the problem.
> > > 
> > > I am sorry for the trouble caused by this. As a work around, you could
> > > also specify the QUIRKS on the Linux command line.
> > > 
> > > > The Monitor is connected via VGA, but also has a DVI interface.
> > > > 
> > > > Maybe the quirk-apply criteria is too unspecific?
> > > 
> > > Hmm, I guess everything is identical but the DVI connector they added to
> > > the VW222U. Though I should have noticed the effect on the VW222S and
> > > did not. :(
> > 
> > Hm.. why should you have noticed the effect on the VW222S? Does it
> > happen there too?
> 
> No, it did not happen there with an Intel 915GM chip. Could you please
> send the `Xorg.0.log`, so that we see what you use. Maybe also a dmesg
> output with `dri.debug=6`.
> 
> > > Could you please send the `edid-decode` output on your system and
> > > `/var/log/Xorg.0.log`.
> > 
> > I attached the xrandr --verbose output and the 
> > # get-edid  | parse-edid
> > output from http://www.polypux.org/projects/read-edid/ which I already
> > had installed. Hope this works for you too.
> >
> > > Also I wonder how this quirk could create such a behavior.
> >
> > Yes. I'm not shure how this could happen. It probably is either a bug
> > somewhere, or it is the 'natural' effect of misconfiguring the vga
> > pipeline.  Maybe someone more knowledgeable than me could make a more
> > educated guess about this.
> 
> What should be done about this? Revert this until the reason for the
> regression is figured out or fix the regression? For the second option,
> Florian could you please create a new ticket?
> 
> 
> Thanks,
> 
> Paul
> 
> 
> > > [1] http://cgit.freedesktop.org/xorg/app/edid-decode/