From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: hjk@linutronix.de
Cc: Tilman Sauerbeck <tilman@code-monkey.de>,
linux-fbdev-devel@lists.sourceforge.net,
xorg@lists.freedesktop.org
Subject: Re: Matrox G550, dual head, 1680x1050
Date: Sun, 04 Mar 2007 20:59:34 -0800 [thread overview]
Message-ID: <45EBA3B6.3060701@vc.cvut.cz> (raw)
In-Reply-To: <200703042247.21590.hjk@linutronix.de>
Hans-Jürgen Koch wrote:
> Am Freitag, 2. März 2007 16:24 schrieb Tilman Sauerbeck:
> Meanwhile I doubt this explanation. Here's what fbset has to say:
>
> $ fbset -fb /dev/fb1 --show
>
> mode "1680x1050-60"
> # D: 135.501 MHz, H: 65.396 kHz, V: 59.997 Hz
> geometry 1680 1050 1680 1050 32
> timings 7380 32 224 32 4 136 4
> rgba 8/16,8/8,8/0,8/24
> endmode
>
> So, even fbset thinks it's 1680x1050. But where does the distortion come
> from???
Can you try setting vxres for second head from 1680 to 1696, or 1728?
Maybe X look at vxres and not at framebuffer line length (what fbset -i
reports for line length?)
If you are using mga driver for second head in X, then probably X driver
does not know correctly what are hardware restrictions for second CRTC
(I think they've changed between G400 and G450), asks for 1680 but gets
1664, and this causes those diagonal lines you see.
Petr
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-05 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703021053.00955.hjk@linutronix.de>
[not found] ` <200703021610.58188.hjk@linutronix.de>
[not found] ` <20070302152414.GC907@code-monkey.de>
2007-03-04 21:47 ` Matrox G550, dual head, 1680x1050 Hans-Jürgen Koch
2007-03-05 4:59 ` Petr Vandrovec [this message]
2007-03-05 6:33 ` Geert Uytterhoeven
2007-03-05 8:09 ` [Linux-fbdev-devel] " Michel Dänzer
2007-03-05 7:34 ` Hans-Jürgen Koch
2007-03-05 20:02 ` Hans-Jürgen Koch
2007-03-06 9:25 ` Petr Vandrovec
2007-03-06 9:38 ` [Linux-fbdev-devel] " Hans-Jürgen Koch
2007-03-06 9:48 ` Geert Uytterhoeven
2007-03-06 11:35 ` Petr Vandrovec
2007-03-05 6:59 ` Tilman Sauerbeck
2007-03-01 23:25 Hans-Jürgen Koch
2007-03-01 23:29 ` Alex Deucher
2007-03-01 23:49 ` Hans-Jürgen Koch
2007-03-01 23:56 ` Hans-Jürgen Koch
2007-03-02 1:49 ` Alex Deucher
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=45EBA3B6.3060701@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=hjk@linutronix.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tilman@code-monkey.de \
--cc=xorg@lists.freedesktop.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).