Summary: | hotkey switching from LFT to CRT gives 'dirty' crt output on i915GM | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Carl Michal <michal> | ||||
Component: | Driver/intel | Assignee: | Alan Hourihane <alanh> | ||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | enhancement | ||||||
Priority: | medium | CC: | mszpak | ||||
Version: | 7.0.0 | Keywords: | patch | ||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Carl Michal
2006-02-06 08:43:11 UTC
Yes, I could definately add a CloneOnHotkey option. I'll try and do this next week. That would be excellent. I'd be happy to test. Before I add it, you should be able to get similar behaviour with the clone option already. Try this... Even though the second screen will be on at startup, if you hotkey, it should cycle through the LFP, CRT and LFP+CRT for clone. Yes, when Clone is set in xorg.conf, it does cycle properly. I guess the only difference CloneOnHotKey option will have from Clone is to start up in the LFP state, but the behaviour otherwise should be identical. There is one other somewhat related issue - this laptop has a 1280x768 widescreen, if I don't remember to reset the resolution before switching it makes the crt very unhappy, but that's probably a problem for another day. Created attachment 4802 [details] [review] Patch for CloneOnHotKey option I've given this a try on my own. The attached patch works for me... Any chance this could get officially added? Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. The bug priority was upgraded (P2->high) with the bugzilla configuration change. I'm Changing the priority back to the normal one. Sorry for the spam. Closing. Please use the new 2.0 driver. |
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.