Bug 2559 - Make xcompmgr compose only fast screens
Summary: Make xcompmgr compose only fast screens
Status: CLOSED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xcompmgr (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-17 01:57 UTC by Mathias Hasselmann
Modified: 2011-10-15 17:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Mathias Hasselmann 2005-02-17 01:57:20 UTC
Have some dual-screen-setup containing of some ultra-fast AGP-card, being more
than sufficient for using composition and some old ultra-slow PCI-card, being
much too slow for using composition. 

When running this server-layout without Xinerama, I can say xcompmgr to manage
only the fast screen, and as a result half of my display looks incredibly great,
whilest remaining fast. 

When activating Xinerama, I cannot activate composition, because the the slow
card dictates the pace then. Well, and my slow card is that slow, that I can
watch the rendering line-by-line then. On both screens.

So me dream would be being able, to tell xcompmgr which Xinerama-monitors to
handle. So I could get eye-candy on the fast card, good performance on both
cards, and I could drag windows between both monitors again. Don't know, if such
a feature is possible, but if it is possible, it would increase adoption of
xcompmgr alot (especially, if it would launch into some smart-mode by default
and loudly refuse to manage slow monitors).

Thanks for listening,
Mathias
Comment 1 Jeremy Huddleston Sequoia 2011-09-24 20:02:12 UTC
I don't see this as being worth the effort.  Maybe 6.5 years ago this may have made sense, but not any more.  If you disagree, feel free to reopen and raise the issue on xorg-devel for 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.