Attachment 92514 Details for Bug 73850 – Patch to allow cloning with HDMI

[patch] Patch to allow cloning with HDMI

0001-drm-i915-Allow-cloning-with-HDMI-on-GMCH-platforms.patch (text/plain), 1.38 KB, created by Ville Syrjala on 2014-01-21 12:26:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Ville Syrjala

Created: 2014-01-21 12:26:55 UTC

Size: 1.38 KB

patch

obsolete

>From 9dfd08bfd68e2076ecf05f3a3e906de063b2b879 Mon Sep 17 00:00:00 2001
>From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= <ville.syrjala@linux.intel.com>
>Date: Tue, 21 Jan 2014 13:38:41 +0200
>Subject: [PATCH] drm/i915: Allow cloning with HDMI on GMCH platforms
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>Cloning between (multiple) HDMI and VGA outputs appears to work just
>fine, on one g4x machine at least. This is the only GMCH machine I
>have that has HDMI outputs, so unfortunately I can't test any others.
>But being an optimist, I can assume it works on other machines as well.
>So let's allow cloning with HDMI outputs on all GMCH platforms.
>
>Signed-off-by: Ville SyrjÃ¤lÃ¤ <ville.syrjala@linux.intel.com>
>---
> drivers/gpu/drm/i915/intel_hdmi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
>index 6db0d9d..d78c368 100644
>--- a/drivers/gpu/drm/i915/intel_hdmi.c
>+++ b/drivers/gpu/drm/i915/intel_hdmi.c
>@@ -1314,7 +1314,7 @@ void intel_hdmi_init(struct drm_device *dev, int hdmi_reg, enum port port)
> 
> 	intel_encoder->type = INTEL_OUTPUT_HDMI;
> 	intel_encoder->crtc_mask = (1 << 0) | (1 << 1) | (1 << 2);
>-	intel_encoder->cloneable = false;
>+	intel_encoder->cloneable = !HAS_PCH_SPLIT(dev);
> 
> 	intel_dig_port->port = port;
> 	intel_dig_port->hdmi.hdmi_reg = hdmi_reg;
>-- 
>1.8.3.2
>

Actions: View | Splinter Review

Attachments on bug 73850: 92514

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.