All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info
Date: Mon, 29 Jan 2007 11:12:57 +1100	[thread overview]
Message-ID: <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> (raw)
In-Reply-To: <20070128160831.fb51347f.akpm@osdl.org>

> > 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..

Dave.

WARNING: multiple messages have this Message-ID (diff)
From: "Dave Airlie" <airlied@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info
Date: Mon, 29 Jan 2007 11:12:57 +1100	[thread overview]
Message-ID: <21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com> (raw)
In-Reply-To: <20070128160831.fb51347f.akpm@osdl.org>

> > 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..

Dave.

-------------------------------------------------------------------------
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

  reply	other threads:[~2007-01-29  0:12 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   ` Dave Airlie [this message]
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
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=21d7e9970701281612q56b694edp6efd1a5556dea3fe@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=giuseppe.bilotta@gmail.com \
    --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: link
Be 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.