Besides the RROutputOrder option determining which screen should become the primary screen in a xinerama setup an option to acutally initilise xinerama mode out of xorg.conf without having to invoke xrandr on session startup manually would be very nice: Option "RROutputOrder" "DVI-D_1, PANEL" screen #1: dvid-d_1 screen #2: panel Option "MonitorLayout" "PANEL, DVI-D_1" Option "CRT2Position" "RightOf" xrandr --output PANEL --left-of DVI-D_1 xrandr --output 1 --right-of 2 The "MonitorLayout" / "CRT2Position" options may be supported in backward compatibility to radeon for this purpose. Such a preconfiguration would leverage the use of programs like krandr, which are used to set the resolution but do not support xinerama setup explicitly. i.e. xrandr --output 2 --resoultion 1920x1200 under the cfg shown above should result in: xrandr --output 2 --resoultion 1920x1200 --left-of 1 i.e. simply remember and restore the previous mode(clone/xinerama) after --output 2 --off & --on
randr already supports static configurations via your xorg.conf. See this page for more info: http://wiki.debian.org/XStrikeForce/HowToRandR12
Elmar, this is not driver specific matter. As mentioned in comment #1 there is already a way to set up a static configuration. This is handled in a layer above the driver to give different drivers a similar look-and-feel. > The "MonitorLayout" / "CRT2Position" options may be supported in backward > compatibility to radeon for this purpose. Such a preconfiguration would > leverage the use of programs like krandr, which are used to set the resolution > but do not support xinerama setup explicitly. I've just taken a brief look - but krandrtray seems to support xinerama on KDE 4.1 at least. (I may be wrong though). > > i.e. xrandr --output 2 --resoultion 1920x1200 > under the cfg shown above should result in: > xrandr --output 2 --resoultion 1920x1200 --left-of 1 > > i.e. simply remember and restore the previous mode(clone/xinerama) after > --output 2 --off & --on This would prescribe a certain behavior regarding the preconfigured setup and thus require a policy. Generally policies assume specific use cases, under different conditions they may render suboptimal results. To make things as flexible as possible the goal is to keep policies out of the Xserver and implement them in a user space program instead. If you feel that static preconfiguration still does not satisfy your needs please bring up your suggestions to the xorg@freedesktop.org ML for general discussion.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.