From: Antonino Daplas <adaplas@pol.net>
To: Fredrik Noring <noring@nocrew.org>
Cc: Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
Ani Joshi <ajoshi@shell.unixbox.com>
Subject: Re: [PATCH] rivafb sync polarity problem?
Date: 20 Jan 2003 00:49:50 +0800 [thread overview]
Message-ID: <1042994847.976.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1042980943.12192.34.camel@h9n1fls20o980.telia.com>
On Sun, 2003-01-19 at 20:55, Fredrik Noring wrote:
> Hi,
>
> It seems the mode below doesn't work with rivafb in Linux 2.4.21-pre2,
> the RGB (TV) screen fail to sync properly. (The equivalent modeline in
> XFree86 4.2 works.)
>
> mode "768x288"
> geometry 768 288 768 288 32
> timings 62500 120 80 20 2 54 2
> hsync low
> vsync low
> endmode
>
Ooops :-) Sorry, I did not notice you were using 288 for your yres, so
62500 is just right.
How bad is the sync problem? It's possible that your horizontal timings
is not divisible by 8? Ie., your hsync_len is 54, but when it's written
to the register, it's just 48. You might want to recalculate the
numbers so you use 54 or 56.
Tony
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-19 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 12:55 [PATCH] rivafb sync polarity problem? Fredrik Noring
2003-01-19 16:25 ` Antonino Daplas
2003-01-19 16:55 ` Fredrik Noring
2003-01-19 16:49 ` Antonino Daplas [this message]
2003-01-19 17:38 ` Fredrik Noring
2003-01-24 19:39 ` James Simmons
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=1042994847.976.3.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=ajoshi@shell.unixbox.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=noring@nocrew.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;
as well as URLs for NNTP newsgroup(s).