From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>, Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: don't always force the panel's fixed_mode
Date: Wed, 08 Feb 2012 23:18:32 +0000 [thread overview]
Message-ID: <c55c5d$1tk001@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120208225310.GF22687@phenom.ffwll.local>
On Wed, 8 Feb 2012 23:53:10 +0100, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Feb 03, 2012 at 05:48:21PM -0200, Paulo Zanoni wrote:
> > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > My laptop has two 1440x900 modes: one is the fixed_mode and the other
> > has different timings. If I use xrandr to switch from the fixed mode to
> > the "other" 1440x900 mode, xrandr will tell me the change was
> > successful, but nothing was actually done: I'm still using the
> > fixed_mode. This patch allows us to use other modes if hdisplay and
> > vdisplay are the same.
> >
> > Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> Hm, I've thought we should only use this to dynamically switch between a
> mode with high refresh rate and one with a low one.
I hesitated for the same reason. Except that by filtering out all modes
except for the one true mode, we prevent the user from being able to
make a choice. They'll invariably make the wrong choice and file a bug,
but nevertheless... ;-)
I also don't think this is the way we want to approach this. The overrides
required for fake LVDS headers would seem to be a superset of this
functionality.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2012-02-08 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 19:48 [PATCH 2/2] drm/i915: don't always force the panel's fixed_mode Paulo Zanoni
2012-02-08 22:53 ` Daniel Vetter
2012-02-08 23:18 ` Chris Wilson [this message]
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='c55c5d$1tk001@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.com \
/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.