From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mike Isely <isely@isely.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Manual control of LVDS pixel formats and dual channel mode
Date: Wed, 13 Apr 2011 08:42:56 +0100 [thread overview]
Message-ID: <1bdc18$k6v1gd@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1104130215590.5473@ivanova.isely.net>
On Wed, 13 Apr 2011 02:27:18 -0500 (CDT), Mike Isely <isely@isely.net> wrote:
> Keep in mind that if the probe action is returning wrong results, that's
> worse than no results. This isn't a question about "supplying missing
> data" so much as it a case of "overriding bad data". Without that fixed
> mode disabling ability, it is very possible that the panel will simply
> be set up wrong with a corrupted display, with no possible means for the
> user to repair the problem. That's what led me to make the change, and
> that same change had been living peacefully in the userspace xorg
> driver, up until the point that UMS had been removed from it. Right now
> without the ability to disable fixed mode there simply *is no*
> workaround.
Point taken. If we can't get a resolution on i915.lvds_fixed_mode= within
the next week, let's focus on the workaround instead.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-13 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:58 [PATCH 2/3] [drm/i915] - Implement ability to disabled LVDS fixed mode Mike Isely
2011-04-12 23:00 ` Manual control of LVDS pixel formats and dual channel mode Chris Wilson
2011-04-12 23:00 ` [PATCH 1/2] drm/i915: Implement direct support for 24 bit LVDS pixel format Chris Wilson
2011-04-12 23:01 ` [PATCH 2/2] drm/i915: Implement manual override of LVDS single/dual channel mode Chris Wilson
2011-04-13 7:27 ` Manual control of LVDS pixel formats and dual " Mike Isely
2011-04-13 7:42 ` Chris Wilson [this message]
2011-04-13 20:44 ` Mike Isely
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='1bdc18$k6v1gd@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=isely@isely.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.