All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: James Simmons <jsimmons@infradead.org>,
	Luca Tettamanti <kronos@people.it>,
	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: Thu, 22 Feb 2007 07:43:26 +0800	[thread overview]
Message-ID: <1172101406.4217.16.camel@daplas> (raw)
In-Reply-To: <cb7bb73a0702061508x767882dcia1b13f85d898b6e7@mail.gmail.com>

On Wed, 2007-02-07 at 00:08 +0100, Giuseppe Bilotta wrote: 
> On 2/6/07, James Simmons <jsimmons@infradead.org> wrote:
> >
> > If you can find post the manufacturer and model number we can place it on
> > the backlist in fbmon. Also we should figure out what is wrong and fix it.
> 
> It's the UltraSharp UXGA display that used to come with Dell Inspiron
> 8200, 15" with a resolution of 1600x1200. I've been looking all around
> for more info on it, but the only things I could find were posts that
> remarked the problems Windows nVidia drivers have with some of these
> (no image when running at 1600x1200), and other posts about banded
> gradients with Windows drivers on Radeon video cards (but I get banded
> gradients also win my nVidia card, on Linux, regardless of which
> driver I use, binary, nv or nouveau).
> 
> As mentioned in another post in this thread, I can't get any info out
> of the i2c busses, because even when I have them available (i.e. after
> loading nvidiafb) I get XXXX all around (on all three of them).
> Suggestions on how to get the information welcome.

Is this the same monitor you posted here?

http://marc.theaimsgroup.com/?l=linux-kernel&m=112807065616218&w=2

If yes, we already have the manufacturer and model code. The main
problem is that the EDID of this display has no sync range (H: 75-75kHz
and V: 60-60Hz).  Extending Hsync from 30-75kHz as a fix to the EDID
block shouldn't be too hard.

I already have a patch for this which I forgot to send to you
before :-).  If you can confirm that this is still the same hardware,
I'll send you a test patch

Tony


WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	Luca Tettamanti <kronos@people.it>,
	linux-kernel@vger.kernel.org,
	James Simmons <jsimmons@infradead.org>,
	Dave Airlie <airlied@gmail.com>
Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info
Date: Thu, 22 Feb 2007 07:43:26 +0800	[thread overview]
Message-ID: <1172101406.4217.16.camel@daplas> (raw)
In-Reply-To: <cb7bb73a0702061508x767882dcia1b13f85d898b6e7@mail.gmail.com>

On Wed, 2007-02-07 at 00:08 +0100, Giuseppe Bilotta wrote: 
> On 2/6/07, James Simmons <jsimmons@infradead.org> wrote:
> >
> > If you can find post the manufacturer and model number we can place it on
> > the backlist in fbmon. Also we should figure out what is wrong and fix it.
> 
> It's the UltraSharp UXGA display that used to come with Dell Inspiron
> 8200, 15" with a resolution of 1600x1200. I've been looking all around
> for more info on it, but the only things I could find were posts that
> remarked the problems Windows nVidia drivers have with some of these
> (no image when running at 1600x1200), and other posts about banded
> gradients with Windows drivers on Radeon video cards (but I get banded
> gradients also win my nVidia card, on Linux, regardless of which
> driver I use, binary, nv or nouveau).
> 
> As mentioned in another post in this thread, I can't get any info out
> of the i2c busses, because even when I have them available (i.e. after
> loading nvidiafb) I get XXXX all around (on all three of them).
> Suggestions on how to get the information welcome.

Is this the same monitor you posted here?

http://marc.theaimsgroup.com/?l=linux-kernel&m=112807065616218&w=2

If yes, we already have the manufacturer and model code. The main
problem is that the EDID of this display has no sync range (H: 75-75kHz
and V: 60-60Hz).  Extending Hsync from 30-75kHz as a fix to the EDID
block shouldn't be too hard.

I already have a patch for this which I forgot to send to you
before :-).  If you can confirm that this is still the same hardware,
I'll send you a test patch

Tony


-------------------------------------------------------------------------
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-02-21 23:40 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
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 [this message]
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=1172101406.4217.16.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=airlied@gmail.com \
    --cc=akpm@osdl.org \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=jsimmons@infradead.org \
    --cc=kronos@people.it \
    --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.