From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, xorg@lists.freedesktop.org
Subject: Re: Radeon X300, radeonfb, dual head
Date: Wed, 18 Apr 2007 15:26:57 +0200 [thread overview]
Message-ID: <200704181526.57746.hjk@linutronix.de> (raw)
In-Reply-To: <4240b9160704180558t6a81f81eoe4a8c768ae6d0929@mail.gmail.com>
Am Mittwoch, 18. April 2007 14:58 schrieb Jerome Glisse:
>
> I am not at all an expert in this radeonfb + X things (somethings i avoid
> to use :)) but i think that radeonfb might get in the way of the X server
That's obvious, but why? Is it a X problem, or is it a radeonfb problem?
Several pages I found on the web suggest that somebody got these working
together. Where does the regression come from? What can I do to help?
> does mergedfb work with a kernel without any framebuffer driver ?
No, I just tried that. I only compiled in vga16, no vesafb, no radeonfb,
but no change in X server behaviour.
But one more interesting thing:
I added
Option "MergedXineramaCRT2IsScreen0" "true"
to my Section "Device". This made kdm show its login window on my screens,
so I could login to KDE. The KDE control center displays everything as it
should be: Desktop 3360x1050, two displays with 1680x1050 each, first display
at 0,0 and second display at 1680,1050.
So obviously the X server "thinks" everything is configured as it should be.
Unfortunately, that's not reality. I still got the same content on both screens.
Hans
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-18 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 12:09 Radeon X300, radeonfb, dual head Hans-Jürgen Koch
2007-04-18 12:58 ` Jerome Glisse
2007-04-18 13:26 ` Hans-Jürgen Koch [this message]
2007-04-18 13:45 ` Michel Dänzer
2007-04-18 15:02 ` [Linux-fbdev-devel] " Hans-Jürgen Koch
2007-04-18 21:20 ` Hans-Jürgen Koch
2007-04-18 21:45 ` Alex Deucher
2007-04-19 7:00 ` Hans-Jürgen Koch
2007-04-19 6:04 ` Michel Dänzer
2007-04-19 8:35 ` Jimmy Jazz
[not found] ` <46272535.5040303@cryosphere.shacknet.nu>
2007-04-19 8:44 ` Hans-Jürgen Koch
2007-04-20 21:54 ` Radeon X300, radeonfb, dual head - conclusion Hans-Jürgen Koch
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=200704181526.57746.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=j.glisse@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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).