Attachment 27701 Details for Bug 22716 – pleaset try the patch on your machine in KMS mode, thanks.

[patch] pleaset try the patch on your machine in KMS mode, thanks.

22716_debug.patch (text/plain), 1.37 KB, created by MaLing on 2009-07-14 18:11:32 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: MaLing

Created: 2009-07-14 18:11:32 UTC

Size: 1.37 KB

patch

obsolete

>diff --git a/drivers/gpu/drm/i915/intel_crt.c b/drivers/gpu/drm/i915/intel_crt.c
>index d6a1a6e..40e3e54 100644
>--- a/drivers/gpu/drm/i915/intel_crt.c
>+++ b/drivers/gpu/drm/i915/intel_crt.c
>@@ -432,9 +432,17 @@ static int intel_crt_get_modes(struct drm_connector *connector)
> 	struct intel_output *intel_output = to_intel_output(connector);
> 	struct i2c_adapter *ddcbus;
> 	struct drm_device *dev = connector->dev;
>+	struct drm_display_mode *mode, *t;
> 
> 
> 	ret = intel_ddc_get_modes(intel_output);
>+	if (ret) {
>+		printk("\n DEBUG: print crt modeline \n");
>+		list_for_each_entry_safe(mode, t, &connector->probed_modes, head)
>+			drm_mode_debug_printmodeline(mode);
>+	} else
>+		printk("\n DEBUG: no modelines available \n");
>+
> 	if (ret || !IS_G4X(dev))
> 		goto end;
> 
>diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>index 57de9a5..6d6743a 100644
>--- a/drivers/gpu/drm/i915/intel_display.c
>+++ b/drivers/gpu/drm/i915/intel_display.c
>@@ -645,7 +645,7 @@ intel_find_best_PLL(const intel_limit_t *limit, struct drm_crtc *crtc,
> 	int err = target;
> 
> 	if (IS_I9XX(dev) && intel_pipe_has_type(crtc, INTEL_OUTPUT_LVDS) &&
>-	    (I915_READ(LVDS) & LVDS_PORT_EN) != 0) {
>+	    (I915_READ(LVDS)) != 0) {
> 		/*
> 		 * For LVDS, if the panel is on, just rely on its current
> 		 * settings for dual-channel.  We haven't figured out how to

Actions: View | Splinter Review

Attachments on bug 22716: 27580 | 27581 | 27701 | 27724 | 27839 | 27873 | 28031 | 28746 | 29099 | 29100

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.