[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1172493985.20842.11.camel@daplas>
Date: Mon, 26 Feb 2007 20:46:25 +0800
From: "Antonino A. Daplas" <adaplas@...il.com>
To: Giuseppe Bilotta <giuseppe.bilotta@...il.com>
Cc: James Simmons <jsimmons@...radead.org>,
Luca Tettamanti <kronos@...ple.it>,
linux-fbdev-devel@...ts.sourceforge.net,
Andrew Morton <akpm@...l.org>, Dave Airlie <airlied@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info
On Sun, 2007-02-25 at 14:16 +0100, Giuseppe Bilotta wrote:
> On 2/25/07, Antonino A. Daplas <adaplas@...il.com> wrote:
> > On Sun, 2007-02-25 at 11:26 +0100, Giuseppe Bilotta wrote:
> > >
> > > Applied. No noticeable difference, in the sense that the EDID debug
> > > output is still the same and so is the snow effect.
> >
> > Here's a temporary workaround:
> >
> > In drivers/video/nvidia/nv_i2c.c:nvidia_probe_i2c_connector(),comment
> > this out:
> >
> > if (par->chan[conn - 1].par)
> > edid = fb_ddc_read(&par->chan[conn - 1].adapter);
> >
> > and make sure CONFIG_FIRMWARE_EDID=y.
>
> With this patch, I don't get any dmesg info about my monitor EDID, but
> I still get the snow. Could it be that there's something else on my
> system which is setting the video to some absurd timings when I
> switchg on the framebuffer console? I'm running an up-to-date debian
> unstable.
>
At this point, I don't know. You're the first person to report this
kind of problem. I'm still studying the nvidiafb and Xorg source code.
Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists