Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info

["Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/