From: Luca Tettamanti <kronos@people.it> To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> Cc: James Simmons <jsimmons@infradead.org>, linux-fbdev-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>, Dave Airlie <airlied@gmail.com>, linux-kernel@vger.kernel.org Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info Date: Sat, 17 Feb 2007 19:14:13 +0100 [thread overview] Message-ID: <20070217181413.GA10134@dreamland.darkstar.lan> (raw) In-Reply-To: <cb7bb73a0702130125r25ddfe33na48ae673d5ce60ae@mail.gmail.com> Il Tue, Feb 13, 2007 at 10:25:41AM +0100, Giuseppe Bilotta ha scritto: > On 2/11/07, Luca Tettamanti <kronos@people.it> wrote: > >Sorry for the delay. > > Ditto! > > It also seemed that my kernel compiling sk1llz had gone AWL, I > couldn't get the newly compiled kernel to run, until I realized the > initrd.img was mislinked. Anyway. > > Your patch has an immediately visible effect of reducing snow: it > seems that now that you fixed the access bug the EDID is properly > /not/ used. dmesg | grep nvidiafb now claims the following: > > """ > > nvidiafb: Device ID: 10de0112 > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > > (it actually gave the "I2C probe failed ..." message on console, but > it's not appearing in the dmesg, obviously, since it's a simple > printk) > > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb: CRTC 1 is currently programmed for DFP > nvidiafb: Using DFP on CRTC 1 > nvidiafb: Panel size is 1600 x 1200 > nvidiafb: Panel is TMDS > nvidiafb: MTRR set to ON > nvidiafb: Flat panel dithering disabled > nvidiafb: PCI nVidia NV11 framebuffer (32MB @ 0xE0000000) > > """ Ok, now I'm confused O_o The patch should be correct, but I fail to see how EDID reading succeded before. > So the EDID still seems to be totally inaccessible (which means I > can't really tell why/when/where it's b0rked). > > Finally, as I mentioned, console still has a little snow. It's barely > perceptible in common console usage because the monitor is mostly > black, but can get annoying with fullscreen apps à la mc. Maybe the snow was caused by the driver hammering the I2C bus. Just guessing... Can you send me X.org log? Luca -- Alcuni pensano che io sia una persona orribile, ma non e` vero. Ho il cuore di un ragazzino - in un vaso sulla scrivania.
WARNING: multiple messages have this Message-ID (diff)
From: Luca Tettamanti <kronos@people.it> To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com> Cc: Andrew Morton <akpm@osdl.org>, linux-fbdev-devel@lists.sourceforge.net, Dave Airlie <airlied@gmail.com>, James Simmons <jsimmons@infradead.org>, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info Date: Sat, 17 Feb 2007 19:14:13 +0100 [thread overview] Message-ID: <20070217181413.GA10134@dreamland.darkstar.lan> (raw) In-Reply-To: <cb7bb73a0702130125r25ddfe33na48ae673d5ce60ae@mail.gmail.com> Il Tue, Feb 13, 2007 at 10:25:41AM +0100, Giuseppe Bilotta ha scritto: > On 2/11/07, Luca Tettamanti <kronos@people.it> wrote: > >Sorry for the delay. > > Ditto! > > It also seemed that my kernel compiling sk1llz had gone AWL, I > couldn't get the newly compiled kernel to run, until I realized the > initrd.img was mislinked. Anyway. > > Your patch has an immediately visible effect of reducing snow: it > seems that now that you fixed the access bug the EDID is properly > /not/ used. dmesg | grep nvidiafb now claims the following: > > """ > > nvidiafb: Device ID: 10de0112 > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > > (it actually gave the "I2C probe failed ..." message on console, but > it's not appearing in the dmesg, obviously, since it's a simple > printk) > > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb 0000:01:00.0: Unable to read EDID block. > nvidiafb: CRTC 1 is currently programmed for DFP > nvidiafb: Using DFP on CRTC 1 > nvidiafb: Panel size is 1600 x 1200 > nvidiafb: Panel is TMDS > nvidiafb: MTRR set to ON > nvidiafb: Flat panel dithering disabled > nvidiafb: PCI nVidia NV11 framebuffer (32MB @ 0xE0000000) > > """ Ok, now I'm confused O_o The patch should be correct, but I fail to see how EDID reading succeded before. > So the EDID still seems to be totally inaccessible (which means I > can't really tell why/when/where it's b0rked). > > Finally, as I mentioned, console still has a little snow. It's barely > perceptible in common console usage because the monitor is mostly > black, but can get annoying with fullscreen apps à la mc. Maybe the snow was caused by the driver hammering the I2C bus. Just guessing... Can you send me X.org log? Luca -- Alcuni pensano che io sia una persona orribile, ma non e` vero. Ho il cuore di un ragazzino - in un vaso sulla scrivania. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-02-17 18:15 UTC|newest] Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-28 10:48 [PATCH] nvidiafb: allow ignoring EDID info Giuseppe Bilotta 2007-01-28 11:05 ` Prakash Punnoor 2007-01-29 0:08 ` Andrew Morton 2007-01-29 0:08 ` Andrew Morton 2007-01-29 0:12 ` [Linux-fbdev-devel] " Dave Airlie 2007-01-29 0:12 ` Dave Airlie 2007-01-29 0:27 ` [Linux-fbdev-devel] " Andrew Morton 2007-01-29 0:27 ` Andrew Morton 2007-01-29 0:29 ` [Linux-fbdev-devel] " Andrew Morton 2007-01-29 0:29 ` Andrew Morton 2007-01-29 0:39 ` [Linux-fbdev-devel] " Dave Airlie 2007-01-29 0:39 ` Dave Airlie 2007-01-29 14:37 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-01-30 20:33 ` Luca Tettamanti 2007-01-30 20:33 ` Luca Tettamanti 2007-02-04 20:17 ` [Linux-fbdev-devel] " Luca Tettamanti 2007-02-04 21:17 ` Giuseppe Bilotta 2007-02-05 20:18 ` Luca Tettamanti 2007-02-05 20:18 ` Luca Tettamanti 2007-02-05 21:28 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-06 21:22 ` James Simmons 2007-02-06 21:22 ` James Simmons 2007-02-07 23:48 ` [Linux-fbdev-devel] " Luca Tettamanti 2007-02-07 23:48 ` Luca Tettamanti 2007-02-08 0:19 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-11 18:17 ` Luca Tettamanti 2007-02-11 18:17 ` Luca Tettamanti 2007-02-13 9:25 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-17 18:14 ` Luca Tettamanti [this message] 2007-02-17 18:14 ` Luca Tettamanti 2007-02-17 18:46 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-08 17:56 ` James Simmons 2007-02-08 17:56 ` James Simmons 2007-02-07 23:57 ` [Linux-fbdev-devel] " Luca Tettamanti 2007-02-07 23:57 ` Luca Tettamanti 2007-02-06 20:37 ` [Linux-fbdev-devel] " James Simmons 2007-02-06 23:08 ` Giuseppe Bilotta 2007-02-21 23:43 ` Antonino A. Daplas 2007-02-21 23:43 ` Antonino A. Daplas 2007-02-22 8:01 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-22 8:40 ` Antonino A. Daplas 2007-02-22 8:40 ` Antonino A. Daplas [not found] ` <cb7bb73a0702220548s55380f7fk995726ffd349823b@mail.gmail.com> [not found] ` <1172153358.4306.17.camel@daplas> 2007-02-22 15:55 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-22 16:21 ` Antonino A. Daplas 2007-02-22 16:21 ` Antonino A. Daplas 2007-02-22 19:08 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-22 23:34 ` Antonino A. Daplas 2007-02-22 23:34 ` Antonino A. Daplas 2007-02-23 13:34 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-23 13:34 ` Giuseppe Bilotta 2007-02-24 7:04 ` [Linux-fbdev-devel] " Antonino A. Daplas 2007-02-24 7:04 ` Antonino A. Daplas 2007-02-24 9:16 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-24 9:16 ` Giuseppe Bilotta 2007-02-24 21:16 ` [Linux-fbdev-devel] " Antonino A. Daplas 2007-02-25 10:26 ` Giuseppe Bilotta 2007-02-25 10:26 ` Giuseppe Bilotta 2007-02-25 11:10 ` [Linux-fbdev-devel] " Antonino A. Daplas 2007-02-25 11:10 ` Antonino A. Daplas 2007-02-25 13:16 ` [Linux-fbdev-devel] " Giuseppe Bilotta 2007-02-25 13:16 ` Giuseppe Bilotta 2007-02-26 12:46 ` [Linux-fbdev-devel] " Antonino A. Daplas 2007-02-22 17:03 ` Antonino A. Daplas 2007-02-22 20:39 ` Luca Tettamanti 2007-02-22 20:39 ` Luca Tettamanti 2007-02-22 23:34 ` [Linux-fbdev-devel] " Antonino A. Daplas 2007-02-22 23:34 ` Antonino A. Daplas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070217181413.GA10134@dreamland.darkstar.lan \ --to=kronos@people.it \ --cc=airlied@gmail.com \ --cc=akpm@osdl.org \ --cc=giuseppe.bilotta@gmail.com \ --cc=jsimmons@infradead.org \ --cc=linux-fbdev-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.