Summary: | [G45] Both HDMI take one pipe | ||
---|---|---|---|
Product: | DRI | Reporter: | Michael Fu <michael.fu> |
Component: | DRM/Intel | Assignee: | ykzhao <yakui.zhao> |
Status: | CLOSED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | medium | CC: | amcnabb, haien.liu, jbarnes, krh, michael.fu, mila.kuchta, zdzichu |
Version: | unspecified | Keywords: | patch |
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | 21120 | ||
Bug Blocks: | |||
Attachments: |
Description
Michael Fu
2009-06-11 21:27:51 UTC
Created attachment 26806 [details]
please try the patch on your machine, then upload output from xrandr --verbose , thanks
In current code we use 1 << I830_OUTPUT_HDMI as clone_mask for HDMIB and HDMIC, by i830_output_clones function, possible_clones of HDMIB and HDMIC will be set as 0x03(1<< 0 | 1 << 1) if they are both created. So if they are both detected, they will share one pipe, in fact spec does not allow them to share one pipe.
Created attachment 26811 [details] output from xrandr --verbose I'm attaching the output from xrandr --verbose with the patches from bug 21120 and 22247 applied. This seems to solve the problem. Hi. I was wondering if there's been any progress on this recently. As I reported earlier, the patch seemed to work. A fix for this was made about a month ago, but I haven't heard whether it's been committed. Is there any progress on this? Will the fix be included in version 2.8.0 of the driver and in the 2.6.31 kernel? It looks like it's so close to being fixed. Thanks. Created attachment 28362 [details] [review] set clone bits in different output device and avoid that one patch is shared by both HDMI The patch is already shipped in Eric's drm-intel-next tree. commit f8aed700c6ec46ddade6570004ce25332283b306 Author: Ma Ling <ling.ma@intel.com> Date: Mon Aug 24 13:50:24 2009 +0800 drm/i915: Set crtc/clone mask in different output devices So this bug will be marked as resolved. Thanks. |
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.