From: Fredrik Noring <noring@nocrew.org>
To: Antonino Daplas <adaplas@pol.net>
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: 19 Jan 2003 17:55:30 +0100 [thread overview]
Message-ID: <1042995331.1071.23.camel@localhost.localdomain> (raw)
In-Reply-To: <1042993221.978.4.camel@localhost.localdomain>
sön 2003-01-19 klockan 17.25 skrev Antonino Daplas:
> The dotclock should be in picoseconds. The above will translate to
> roughly 16MHz only.
Yep. The corresponding modeline in XFree86 4.2 is:
Modeline "768x288" 16.0 768 848 902 1022 288 290 292 312 -hsync -vsync
It's a mode designed for regular PAL TV output (through RGB-SCART) and
it works excellent with XFree86 4.2. The corresponding modeline for NTSC
looks like this:
Modeline "768x240" 16.0 768 848 902 1022 240 243 244 261 -hsync -vsync
Hopefully, rivafb will support interlace some day and then these
modelines will also work:
ModeLine "768x485" 16.0 768 848 902 1022 485 491 496 525 -hsync -vsync interlace
ModeLine "768x576" 16.0 768 848 902 1022 576 580 585 625 -hsync -vsync interlace
(PAL and NTSC respectively.)
For some reason, rivafb will not render any of these modes properly a.t.m.
Fredrik
-------------------------------------------------------
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:54 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 [this message]
2003-01-19 16:49 ` Antonino Daplas
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=1042995331.1071.23.camel@localhost.localdomain \
--to=noring@nocrew.org \
--cc=adaplas@pol.net \
--cc=ajoshi@shell.unixbox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.