From: Adam Jackson <ajax@redhat.com>
To: David Airlie <airlied@redhat.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/edid: Adding common CVT inferred modes when monitor allows range limited ones trough EDID.
Date: Fri, 13 Apr 2012 13:16:31 -0400 [thread overview]
Message-ID: <4F885F6F.10104@redhat.com> (raw)
In-Reply-To: <09c7ef24-9342-4ae0-8f10-a0ba20dc3bb9@zmail16.collab.prod.int.phx2.redhat.com>
On 4/13/12 11:25 AM, David Airlie wrote:
> I'm still intrigued about what hardware exists with a panel with a native mode it doesn't describe.
>
> How are we to know what the panel preferred mode is in this case?
>
> Or is this for larger panels wanting to use smaller modes?
AFAICT, yes, this last one. For asymmetric cloning, a misfeature
exceeded in stupidity only by panning. Because you have a panel with a
bizarre size and then an external that's sane, and you try to clone, and
even though the bizarre size would fit it's not available on both mode
lists.
And at _that_ point, this isn't an EDID parser issue at all, it's driver
policy.
- ajax
next prev parent reply other threads:[~2012-04-13 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 0:59 [PATCH] drm/edid: Adding common CVT inferred modes when monitor allows range limited ones trough EDID Rodrigo Vivi
2012-04-12 16:03 ` Adam Jackson
2012-04-12 16:33 ` [Intel-gfx] " Takashi Iwai
2012-04-12 23:09 ` Rodrigo Vivi
2012-04-13 14:14 ` Adam Jackson
2012-04-13 14:29 ` Takashi Iwai
2012-04-13 14:35 ` Dave Airlie
2012-04-13 15:13 ` Takashi Iwai
2012-04-13 15:30 ` Alex Deucher
2012-04-13 15:41 ` Takashi Iwai
2012-04-13 15:52 ` Alex Deucher
2012-04-13 16:31 ` Adam Jackson
2012-04-13 16:48 ` Takashi Iwai
2012-04-13 14:55 ` Adam Jackson
2012-04-13 15:20 ` Takashi Iwai
2012-04-13 15:25 ` David Airlie
2012-04-13 17:16 ` Adam Jackson [this message]
2012-04-13 19:05 ` Rodrigo Vivi
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=4F885F6F.10104@redhat.com \
--to=ajax@redhat.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tiwai@suse.de \
/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.