All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Hans-Jürgen Koch" <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: Tue, 06 Mar 2007 01:25:15 -0800	[thread overview]
Message-ID: <45ED337B.6010209@vc.cvut.cz> (raw)
In-Reply-To: <200703052102.31786.hjk@linutronix.de>

Hans-Jürgen Koch wrote:
> Am Montag, 5. März 2007 05:59 schrieb Petr Vandrovec:
> 
>> 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?)
>>
> 
> Here are more details:
> 
> 1.) I boot my kernel (vanilla 2.6.20.1) with the following parameters:
> 
> video=matroxfb:outputs:120,pixclock:7380,xres:1680,yres:1050,upper:32,
>                lower:4,left:32,right:224,hslen:136,vslen:4,depth:32
> 
> This initializes the primary head correctly. The second head is probably 
> wrong, because the monitor's on screen message complains about a non-ideal 
> resolution.

Second head always starts in 640x480/32bpp.  You have to use fbset to 
switch it to different mode, so matroxfb works fine as far as I can tell.

> As you can see, the second monitor fell back to VGA resolution, but the logs 
> tell that X thinks it successfully switched to 1680x1050. The KDE control 
> center reports the same. The image on the second monitor is distorted.

Because X (mga driver) was programming hardware...

> 4.) I then issue the following command:
> 
> $ fbset -fb /dev/fb1 -g 1680 1050 1696 1050 32 -t 7380 224 32 32 4 136 4
> 
> With that, the image on the second monitor immediately becomes clear, and I 
> have a fully working xinerama configuration then.

Yes, and this corrects X programming mistake.

> As far as I can see, fbset is the only way to initialize the second head 
> properly. Neither matroxfb nor mga do it correctly with 1680x1050.

Well, fbset == matroxfb, so I do not quite understand your complaint.
							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

  reply	other threads:[~2007-03-06  9:26 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
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 [this message]
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=45ED337B.6010209@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 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.