From: Adam Jackson <ajax@redhat.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next trees
Date: Mon, 24 Sep 2012 10:34:12 -0400 [thread overview]
Message-ID: <1348497252.15901.46.camel@atropine> (raw)
In-Reply-To: <505E916F.7000803@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1271 bytes --]
On Sat, 2012-09-22 at 23:34 -0500, Ian Pilcher wrote:
> On 09/12/2012 08:44 PM, Dave Airlie wrote:
> > Ajax, I think Ian still has an open request on how to proceed with the
> > infoframes quirk nightmare.
>
> Indeed.
I'm sorry, I thought I was clearer. Daniel posted a patch to fix the
Intel driver for this:
http://lists.freedesktop.org/archives/intel-gfx/2012-August/020046.html
Which I didn't entirely ack, but which is essentially right. That's
what we should do; and having done so, if I understand things correctly,
there's no need for any quirks here at all.
Is there something I'm missing?
But also:
> > * Leave both flags, because both are accurate. The display is confused
> > by any InfoFrames (audio or AVI), and it is reporting non-existent
> > audio capabilities. The fact that the combination of the two flags
> > makes the display work with Intel GPUs is a happy/sad/neutral
> > accident, and the driver's behavior is still considered broken.
I haven't actually seen the EDID block for this display, I don't
believe, so I'm not sure whether the "non-existent" part of this is even
accurate, or whether we're just parsing things incorrectly. There's a
reason I keep a standalone parser around.
- ajax
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-09-24 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 1:44 -next trees Dave Airlie
2012-09-13 22:10 ` Alex Deucher
2012-09-17 16:25 ` Rob Clark
2012-09-22 9:43 ` Paul Menzel
2012-09-23 4:34 ` Ian Pilcher
2012-09-24 14:34 ` Adam Jackson [this message]
2012-09-25 18:47 ` Ian Pilcher
2012-09-26 17:00 ` Adam Jackson
2012-09-26 21:04 ` Ian Pilcher
2012-09-27 14:42 ` Daniel Vetter
2012-09-28 7:03 ` [PATCH v5 0/3] Enhanced EDID quirk functionality Ian Pilcher
2012-09-28 7:03 ` [PATCH v5 1/3] drm: Add user-defined EDID quirks capability Ian Pilcher
2012-10-09 12:15 ` Jani Nikula
2012-10-09 15:13 ` Ian Pilcher
2012-10-10 6:31 ` Jani Nikula
2012-09-28 7:03 ` [PATCH v5 2/3] drm: Add EDID quirk to disable HDMI InfoFrames Ian Pilcher
2012-09-28 7:03 ` [PATCH v5 3/3] drm: Add EDID quirk for LG L246WP Ian Pilcher
2012-10-08 23:22 ` [PATCH v5 0/3] Enhanced EDID quirk functionality Ian Pilcher
2012-10-09 15:18 ` Adam Jackson
2016-09-28 3:31 -next trees Dave Airlie
2016-09-28 21:07 ` Alex Deucher
2016-09-29 9:47 ` Daniel Vetter
2016-09-29 16:23 ` Thierry Reding
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=1348497252.15901.46.camel@atropine \
--to=ajax@redhat.com \
--cc=arequipeno@gmail.com \
--cc=dri-devel@lists.freedesktop.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 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.