mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>
To: "Antonino A. Daplas" <adaplas@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 16:55:56 +0100	[thread overview]
Message-ID: <cb7bb73a0702220755y3eb2e5b1r8e7908ae0c1720c9@mail.gmail.com> (raw)
In-Reply-To: <1172153358.4306.17.camel@daplas>

On 2/22/07, Antonino A. Daplas <adaplas@gmail.com> wrote:
>
> Ah, my fault.  Apply this patch on top.

We're getting closer! The patch now works, and the dmesg has the following info:


ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level,
low) -> IRQ 11
nvidiafb: Device ID: 10de0112
fbmon: The EDID Block of Manufacturer: SHP Model: 0x138e is known to be broken,
fbmon: trying to fix monitor timings
nvidiafb: EDID found from BUS2
========================================
Display Information (EDID)
========================================
   EDID Version 1.3
   Manufacturer: SHP
   Model: 138e
   Serial#: 0
   Year: 1990 Week 0
   Display Characteristics:
      Monitor Operating Limits: From EDID
           H: 30-75KHz V: 60-60Hz DCLK: 170MHz
      Digital Display Input
      Sync:
      Max H-size in cm: 30
      Max V-size in cm: 23
      Gamma: 2.20
      DPMS: Active no, Suspend yes, Standby yes
      RGB Color Display
      Chroma
         RedX:     0.599 RedY:     0.335
         GreenX:   0.313 GreenY:   0.552
         BlueX:    0.150 BlueY:    0.145
         WhiteX:   0.313 WhiteY:   0.328
      First DETAILED Timing is preferred
   Detailed Timings
      160 MHz 1600 1664 1856 2112 1200 1201 1204 1250 -HSync -VSync

   Supported VESA Modes
      Manufacturer's mask: 0
   Standard Timings
      1600x1200@60Hz
========================================
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
Console: switching to colour frame buffer device 200x75
nvidiafb: PCI nVidia NV11 framebuffer (32MB @ 0xE0000000)




However, I'm still getting the same snowy effects, which doesn't come
as a surprise since the actual mode timings used are just the same ...


-- 
Giuseppe "Oblomov" Bilotta

  parent reply	other threads:[~2007-02-22 15:55 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-28 10:48 Giuseppe Bilotta
2007-01-28 11:05 ` Prakash Punnoor
2007-01-29  0:08 ` Andrew Morton
2007-01-29  0:12   ` [Linux-fbdev-devel] " Dave Airlie
2007-01-29  0:27     ` Andrew Morton
2007-01-29  0:29     ` Andrew Morton
2007-01-29  0:39       ` Dave Airlie
2007-01-29 14:37         ` Giuseppe Bilotta
2007-01-30 20:33           ` Luca Tettamanti
2007-02-04 20:17             ` Luca Tettamanti
2007-02-04 21:17               ` Giuseppe Bilotta
2007-02-05 20:18                 ` Luca Tettamanti
2007-02-05 21:28                   ` Giuseppe Bilotta
2007-02-06 21:22                     ` James Simmons
2007-02-07 23:48                       ` Luca Tettamanti
2007-02-08  0:19                         ` Giuseppe Bilotta
2007-02-11 18:17                           ` Luca Tettamanti
2007-02-13  9:25                             ` Giuseppe Bilotta
2007-02-17 18:14                               ` Luca Tettamanti
2007-02-17 18:46                                 ` Giuseppe Bilotta
2007-02-08 17:56                         ` James Simmons
2007-02-07 23:57                     ` Luca Tettamanti
2007-02-06 20:37               ` James Simmons
2007-02-06 23:08                 ` Giuseppe Bilotta
2007-02-21 23:43                   ` Antonino A. Daplas
2007-02-22  8:01                     ` Giuseppe Bilotta
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                             ` Giuseppe Bilotta [this message]
2007-02-22 16:21                               ` Antonino A. Daplas
2007-02-22 19:08                                 ` Giuseppe Bilotta
2007-02-22 23:34                                   ` Antonino A. Daplas
2007-02-23 13:34                                     ` Giuseppe Bilotta
2007-02-24  7:04                                       ` Antonino A. Daplas
2007-02-24  9:16                                         ` Giuseppe Bilotta
2007-02-24 21:16                                           ` Antonino A. Daplas
2007-02-25 10:26                                             ` Giuseppe Bilotta
2007-02-25 11:10                                               ` Antonino A. Daplas
2007-02-25 13:16                                                 ` Giuseppe Bilotta
2007-02-26 12:46                                                   ` Antonino A. Daplas
2007-02-22 17:03                               ` Antonino A. Daplas
2007-02-22 20:39                       ` Luca Tettamanti
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=cb7bb73a0702220755y3eb2e5b1r8e7908ae0c1720c9@mail.gmail.com \
    --to=giuseppe.bilotta@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=airlied@gmail.com \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®