public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>, airlied@linux.ie
Cc: eric@anholt.net, jesse.barnes@intel.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	gregkh@suse.de
Subject: Re: [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard
Date: Mon, 03 Jan 2011 14:54:53 +0000	[thread overview]
Message-ID: <b7da2f$q1ffv6@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <4D21DC41.8070408@t-online.de>

On Mon, 03 Jan 2011 15:25:05 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> The AOpen i915GMm-HFS is a desktop motherboard for the Intel Pentium M.
> A mobile chipset is used
> (Intel 915GM / ICH6-M). Kernel 2.6.31.14 works fine for that mobo, but
> from 2.6.32 on graphics support
> is broken because the i915 driver "detects" an lvds device with a
> resolution of 1024x768 pixels that in reality
> is not present. Unfortunately the driver assumes that the "detected"
> lvds is the primary screen and uses the
> wrong resolution also for the real VGA and DVI connectors.

Can you try:

diff --git a/drivers/gpu/drm/i915/intel_i2c.c
b/drivers/gpu/drm/i915/intel_i2c.c
index 58040f6..111128d 100644
--- a/drivers/gpu/drm/i915/intel_i2c.c
+++ b/drivers/gpu/drm/i915/intel_i2c.c
@@ -384,7 +384,7 @@ int intel_setup_gmbus(struct drm_device *dev)
                bus->reg0 = i | GMBUS_RATE_100KHZ;
 
                /* XXX force bit banging until GMBUS is fully debugged */
-               bus->force_bit = intel_gpio_create(dev_priv, i);
+               //bus->force_bit = intel_gpio_create(dev_priv, i);
        }
 
        intel_i2c_reset(dev_priv->dev);
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-01-03 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 14:25 [PATCH] Fix i915 drm regression on AOpen i915GMm-HFS motherboard Knut Petersen
2011-01-03 14:54 ` Chris Wilson [this message]
2011-01-03 18:12   ` Knut Petersen
2011-01-03 19:45     ` Linus Torvalds
2011-01-03 19:59       ` Chris Wilson
2011-01-03 20:26         ` Linus Torvalds
2012-04-04 16:23           ` Jean Delvare
2011-01-03 23:09         ` Knut Petersen
2011-01-03 23:22           ` Chris Wilson
2011-01-04  0:35             ` Knut Petersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='b7da2f$q1ffv6@fmsmga001.fm.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=Knut_Petersen@t-online.de \
    --cc=airlied@linux.ie \
    --cc=eric@anholt.net \
    --cc=gregkh@suse.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox