From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Martin Wilck <martin.wilck@fujitsu-siemens.com>
Subject: Re: Default timings in vga16fb driver
Date: Thu, 25 Nov 2004 00:16:23 +0800 [thread overview]
Message-ID: <200411250016.25813.adaplas@hotpop.com> (raw)
In-Reply-To: <41A36DA5.8090200@fujitsu-siemens.com>
On Wednesday 24 November 2004 01:04, Martin Wilck wrote:
> Hello,
>
> I am wondering about the standard mode timings for the 640x480@60 mode
> in vga16fb driver (vga16fb_defined):
>
> .pixclock = 39721,
> .left_margin = 48,
> .right_margin = 16,
> .upper_margin = 39,
> .lower_margin = 8,
> .hsync_len = 96,
> .vsync_len = 2,
> .vmode = FB_VMODE_NONINTERLACED,
>
> IMO this corresponds to a total screen height of 529 which is different
> from the value 525 which is normally used (eg in X Windows). What is the
> reason for this? Is it possible that the value for "upper_margin" should
Possibly, because nobody really complained that the modeline is slightly
off. Most users have variable sync displays and should have no problem
display a slightly off modeline.
>
> be 35 rather than 39?
> I am asking because we have encountered a video device that obviously
> has problems displaying the standard mode of the vga16fb driver.
>
Did the device work correctly after changing the modeline?
> More detail:
>
> Unless I'm mistaken, the above translates into an XFree86 modeline
> ModeLine "640x480" 25.175 640 656 752 800 480 488 490 529
Yes, the above does give a slightly off vert refresh rate of 59.49
(800*529)/25175000
>
> The standard XFree86 modeline for this mode, however, looks like this:
> (same in drivers/video/modedb.c)
> ModeLine "640x480" 25.175 640 664 760 800 480 491 493 525
This one gives a refresh rate of 59.94 which is the closest we can get to a
60 Hz refresh.
>
> The description at http://www.epanorama.net/documents/pc/vga_timing.html.
> would suggest:
> ModeLine "640x480" 25.175 640 656 752 800 480 490 492 525
And this one too.
>
> I apologize if I'm overlooking something.
I don't think you overlooked anything. The default modeline of vga16fb
should be corrected.
Tony
-------------------------------------------------------
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-24 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:04 Default timings in vga16fb driver Martin Wilck
2004-11-24 16:16 ` Antonino A. Daplas [this message]
2004-11-25 14:55 ` Martin Wilck
2004-11-25 19:51 ` Antonino A. Daplas
2004-11-26 9:11 ` Geert Uytterhoeven
2004-11-27 14:53 ` FB_EVENT (blank and unblank?) Richard Purdie
2004-11-27 22:43 ` Antonino A. Daplas
2004-11-27 23:59 ` Richard Purdie
2004-11-28 0:24 ` Antonino A. Daplas
2004-11-28 0:59 ` Richard Purdie
2004-11-28 1:14 ` Antonino A. Daplas
2004-11-29 22:36 ` fbdev: Add FB_EVENT_BLANK to notify listeners of a blanking status change Richard Purdie
2004-11-29 23:29 ` Antonino A. Daplas
2004-11-29 10:53 ` cursor color changes ramprasad
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=200411250016.25813.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=martin.wilck@fujitsu-siemens.com \
/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).