From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933007AbXA2A2F (ORCPT ); Sun, 28 Jan 2007 19:28:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933018AbXA2A2F (ORCPT ); Sun, 28 Jan 2007 19:28:05 -0500 Received: from smtp.osdl.org ([65.172.181.24]:43433 "EHLO smtp.osdl.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933007AbXA2A2C (ORCPT ); Sun, 28 Jan 2007 19:28:02 -0500 Date: Sun, 28 Jan 2007 16:27:56 -0800 From: Andrew Morton To: "Dave Airlie" Cc: linux-fbdev-devel@lists.sourceforge.net, "Giuseppe Bilotta" , linux-kernel@vger.kernel.org Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info Message-Id: <20070128162756.0b123062.akpm@osdl.org> In-Reply-To: <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> References: <20070128160831.fb51347f.akpm@osdl.org> <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 29 Jan 2007 11:12:57 +1100 "Dave Airlie" wrote: > > > Some nVidia video cards have broken EDID information. Using nvidiafb > > > with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console > > > framebuffer to use wrong timing information, causing the display to be > > > extremely 'snowy'. Since most distribution kernels are compiled with > > > CONFIG_FB_NVIDIA_I2C enabled, this prevents usage of the nvidia > > > framebuffer on said broken system without recompiling the kernel > > > (or at least the nvidiafb module). > > > > > > Solve the issue by introducing a new boolean module parameter (useedid) > > > which can be set to 0 to prevent the driver from using the EDID > > > information. > > > > > > If this patch is accepted, we can probably get rid of CONFIG_FB_NVIDIA_I2C > > > altogether. > > > > > > > That's a pretty sad solution. Is it possible to detect these bad cards at > > runtime via ther behaviour? If not, can we generate a blacklist for the > > known-bad cards based on PCI IDs or something? > > > > Because most users won't even be aware of the module option: they'll just > > know that their card doesn't work right. > > This isn't a card problem this is a monitor problem, the card just > passes through the edid data from the monitor... or else the > programming of the card registers from edid is wrong.. > oh. I'll take that as an ack :( (where'd my cc go?) From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info Date: Sun, 28 Jan 2007 16:27:56 -0800 Message-ID: <20070128162756.0b123062.akpm@osdl.org> References: <20070128160831.fb51347f.akpm@osdl.org> <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> Reply-To: linux-fbdev-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.91] helo=mail.sourceforge.net) by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43) id 1HBKNO-0005zD-71 for linux-fbdev-devel@lists.sourceforge.net; Sun, 28 Jan 2007 16:28:02 -0800 Received: from smtp.osdl.org ([65.172.181.24]) by mail.sourceforge.net with esmtp (Exim 4.44) id 1HBKNM-0003pb-RF for linux-fbdev-devel@lists.sourceforge.net; Sun, 28 Jan 2007 16:28:02 -0800 In-Reply-To: <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-fbdev-devel-bounces@lists.sourceforge.net Errors-To: linux-fbdev-devel-bounces@lists.sourceforge.net To: Dave Airlie Cc: Giuseppe Bilotta , linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Mon, 29 Jan 2007 11:12:57 +1100 "Dave Airlie" wrote: > > > Some nVidia video cards have broken EDID information. Using nvidiafb > > > with CONFIG_FB_NVIDIA_I2C enabled on these systems causes the console > > > framebuffer to use wrong timing information, causing the display to be > > > extremely 'snowy'. Since most distribution kernels are compiled with > > > CONFIG_FB_NVIDIA_I2C enabled, this prevents usage of the nvidia > > > framebuffer on said broken system without recompiling the kernel > > > (or at least the nvidiafb module). > > > > > > Solve the issue by introducing a new boolean module parameter (useedid) > > > which can be set to 0 to prevent the driver from using the EDID > > > information. > > > > > > If this patch is accepted, we can probably get rid of CONFIG_FB_NVIDIA_I2C > > > altogether. > > > > > > > That's a pretty sad solution. Is it possible to detect these bad cards at > > runtime via ther behaviour? If not, can we generate a blacklist for the > > known-bad cards based on PCI IDs or something? > > > > Because most users won't even be aware of the module option: they'll just > > know that their card doesn't work right. > > This isn't a card problem this is a monitor problem, the card just > passes through the edid data from the monitor... or else the > programming of the card registers from edid is wrong.. > oh. I'll take that as an ack :( (where'd my cc go?) ------------------------------------------------------------------------- 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