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 19:23:40 +0000 [thread overview]
Message-ID: <200411231923.40572.andrew@walrond.org> (raw)
In-Reply-To: <200411240226.03203.adaplas@hotpop.com>
On Tuesday 23 Nov 2004 18:26, Antonino A. Daplas wrote:
>
> For now, I'll add checks during the initializatiion that will refuse modes
> greater than the panel size.
>
Even if they are listed in the list of supported modes and detailed modes in
the EDID?
My (dvi) edid lists valid modes of
First DETAILED Timing is preferred
Supported VESA Modes
720x400@70Hz
640x480@60Hz
640x480@67Hz
640x480@72Hz
640x480@75Hz
800x600@56Hz
800x600@60Hz
800x600@72Hz
800x600@75Hz
832x624@75Hz
1024x768@60Hz
1024x768@70Hz
1024x768@75Hz
1280x1024@75Hz
1152x870@75Hz
Manufacturer's mask: 0
Standard Timings
1280x1024@60Hz
1024x819@85Hz
800x640@85Hz
640x512@85Hz
Detailed Timings
65 MHz 1024 1040 1104 1344 768 781 783 817 -HSync -VSync
162 MHz 1600 1664 1856 2160 1200 1201 1204 1250 +HSync +VSync
Ok, the first detailed mode is preferred, but the second is equal;y supported.
> Unfortunately, without any docs on how to adjust the default panel size,
> you will be limited to this resolution only.
I'm a bit confused now. On one hand you seem to be testing for and rejecting
modes > panel size in the driver; But here I infer that the hardware won't
accept these modes unless we can somehow reset the panel size first?
>
> Does vesafb work in x86_64? If it does you can add this in your
> commandline:
>
> vga=0x307
>
> 0x306 is the code for 1280x1024, see Documentation/fb/vesafb.txt.
>
> Then check your dmesg if the panel size also changed. If it did, then
> you can do this:
>
> vga=0x307 video=nvidiafb:1280x1024@60.
And this is just a possible means of tricking the hardware into adjusting the
panel size for us?
Sorry about all the questions, but I want to understand so I can investigate
further. Its frustrating having massively expensive screens with the latest
digital dvi cables behaving like a cheap 1024x768 monitor ;)
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/
next prev parent reply other threads:[~2004-11-23 19:23 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
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 [this message]
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=200411231923.40572.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).