linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: Rivafb won't work with DVI connector
Date: Tue, 23 Nov 2004 12:32:57 +0000	[thread overview]
Message-ID: <200411231232.57420.andrew@walrond.org> (raw)
In-Reply-To: <200411230950.24311.adaplas@hotpop.com>

On Tuesday 23 Nov 2004 01:50, Antonino A. Daplas wrote:
> On Tuesday 23 November 2004 07:47, Andrew Walrond wrote:
> >
> > Note the erroneous panel detection; this is a 1600x1200 tft lcd. The
> > panel is detected as 1024x768 in every following case.
>
> The panel size is programmed by the BIOS, not sure what what we can do
> about that.  So even if your display supports 1600x1200, you're still
> limited to 1024x768.

What, the video-card BIOS? Shouldn't it get the correct info from the EDID?

andrew@orac fbdev $ read-edid-1.4.1/parse-edid edid.dsub.32
read-edid-1.4.1/parse-edid: parse-edid version 1.4.1
read-edid-1.4.1/parse-edid: EDID checksum passed.

        # EDID version 1 revision 3
Section "Monitor"
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
        Identifier "iiyama "
        VendorName "IVM"
        ModelName "iiyama "
        # Block type: 2:0 3:fd
        HorizSync 30-80
        VertRefresh 56-85
        # Max dot clock (video bandwidth) 170 MHz
        # Block type: 2:0 3:fc
        # DPMS capabilities: Active off:yes  Suspend:yes  Standby:yes

        Mode    "1024x768"      # vfreq 59.196Hz, hfreq 48.363kHz
                DotClock        65.000000
                HTimings        1024 1040 1104 1344
                VTimings        768 781 783 817
                Flags   "-HSync" "-VSync"
        EndMode
        Mode    "1600x1200"     # vfreq 60.000Hz, hfreq 75.000kHz
                DotClock        162.000000
                HTimings        1600 1664 1856 2160
                VTimings        1200 1201 1204 1250
                Flags   "+HSync" "+VSync"
        EndMode
        # Block type: 2:0 3:fd
        # Block type: 2:0 3:fc
EndSection

>
> It seems that EDID block is not detected whether digital or analog. I think
> I missed a Kconfig changeset. Should be fixed with the included patch.
>
> Select y to FB_NVIDIA_I2C.
>

Ok, with your incremental patch, DSUB connection and no kernel params, the 
kernel boots into a corruption free 1600x1200 (200xwhatever) console with two 
nice penguins, after detecting EDIDs on BUS2 and BUS3.
Unfortunately, it then  Oops's like this: (copied by hand)

 Oops : PREEMPT SMP

 tty_open+342  chrdev_open+457
 dentry_open+315 filp_open+62
 get_unused_fd+244 sys_open+76
 init+652   child_rip+8
 init+0    child_rip+0

 RIP: check_tty_count+58

Booting with DVI connection and no params gives me a corruption free 1024x768 
console with two nice penguins. It also then Oopses in an identical way to 
above.

Getting closer...

Andrew


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-11-23 12:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 11:37 Rivafb won't work with DVI connector Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52   ` Andrew Walrond
2004-11-22  0:11     ` Antonino A. Daplas
2004-11-22  9:23       ` Andrew Walrond
2004-11-22  9:43         ` Andrew Walrond
2004-11-22 22:13           ` Antonino A. Daplas
2004-11-22 23:47             ` Andrew Walrond
2004-11-22 23:54               ` Andrew Walrond
2004-11-23  1:50               ` Antonino A. Daplas
2004-11-23 12:32                 ` Andrew Walrond [this message]
2004-11-23 14:28                   ` Antonino A. Daplas
2004-11-23 15:09                     ` Andrew Walrond
2004-11-23 15:18                       ` Antonino A. Daplas
2004-11-23 16:08                         ` Andrew Walrond
2004-11-23 17:07                           ` Antonino A. Daplas
2004-11-23 18:01                             ` Andrew Walrond
2004-11-23 18:26                               ` Antonino A. Daplas
2004-11-23 19:00                                 ` Andrew Walrond
2004-11-23 19:07                                   ` Andrew Walrond
2004-11-23 19:23                                 ` Andrew Walrond
2004-11-23 19:59                                   ` Geert Uytterhoeven
2004-11-23 20:53                                     ` Andrew Walrond
2004-11-23 22:44                                       ` Antonino A. Daplas
2004-11-23 23:59                                         ` Andrew Walrond
2004-11-24 22:38                                         ` Andrew Walrond
2004-11-23 20:21                                   ` Chad Daelhousen
2004-11-24 23:01                                 ` Andrew Walrond
  -- strict thread matches above, loose matches on Subject: below --
2004-11-25  0:07 Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16   ` Antonino A. Daplas
2004-11-26 14:09   ` Antonino A. Daplas
2004-11-27 12:40     ` Andrew Walrond
2004-11-27 18:29       ` Michel Dänzer
2004-11-27 22:35         ` Andrew Walrond
2004-11-27 22:43       ` 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=200411231232.57420.andrew@walrond.org \
    --to=andrew@walrond.org \
    --cc=adaplas@hotpop.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).