From: Daniel Vetter <daniel@ffwll.ch>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next queue and EDID stuff
Date: Wed, 29 Aug 2012 09:56:16 +0200 [thread overview]
Message-ID: <20120829075616.GA5278@phenom.ffwll.local> (raw)
In-Reply-To: <503D9810.60104@gmail.com>
On Tue, Aug 28, 2012 at 11:18:24PM -0500, Ian Pilcher wrote:
> On 08/28/2012 07:13 PM, Adam Jackson wrote:
> > On 8/28/12 7:33 PM, Ian Pilcher wrote:
> >> Actually, I believe that the error is probably in the Intel driver. As
> >> I understand it, it shouldn't be sending audio InfoFrames to a non-HDMI
> >> display.
> >
> > If that's the case then I'd still say "we're doing something else wrong
> > here". Quirks - at least at the core drm level - are not for working
> > around broken drivers, they're for working around broken displays.
>
> And I'd agree.
>
> (Although I suppose one *could* argue that the display is broken in 2
> ways -- it reports audio capabilities that aren't really there, and it
> gets confused by any InfoFrames -- AVI or audio.)
>
> I don't have the knowledge or time to fix the Intel driver, but I've
> always planned to at least bugzilla the issue. I can't reasonably do
> so, however, until the user-defined quirks infrastructure is in place,
> so that the behavior can be demonstrated.
>
> If you prefer to leave the display broken with Intel GPUs, you can
> always just remove the EDID_QUIRK_NO_AUDIO flag:
Wrt intel infoframes issues: Have you retested on latest 3.6-rc kernels?
We've fixed quite a few bugs for our infoframe support recently ...
-Daniel
>
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -160,6 +160,10 @@ union edid_quirk
> edid_quirk_list[EDID_QUIRK_LIST_SIZE] = {
> { { { { EDID_MFG_ID('V', 'S', 'C'), cpu_to_le16(5020) } },
> EDID_QUIRK_FORCE_REDUCED_BLANKING } },
>
> + /* LG L246WP */
> + { { { { EDID_MFG_ID('G', 'S', 'M'), cpu_to_le16(0x563f) } },
> + EDID_QUIRK_DISABLE_INFOFRAMES } },
> +
> /*
> * When adding built-in quirks, please adjust EDID_QUIRK_LIST_SIZE to
> * provide some room for user-supplied quirks.
>
> --
> ========================================================================
> Ian Pilcher arequipeno@gmail.com
> "If you're going to shift my paradigm ... at least buy me dinner first."
> ========================================================================
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-08-29 7:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 23:50 -next queue and EDID stuff Dave Airlie
2012-08-27 20:24 ` Adam Jackson
2012-08-27 20:34 ` Alex Deucher
2012-08-27 20:47 ` Adam Jackson
2012-08-27 21:51 ` Daniel Vetter
2012-08-27 23:04 ` Ben Skeggs
2012-08-28 23:33 ` Ian Pilcher
2012-08-29 0:13 ` Adam Jackson
2012-08-29 4:18 ` Ian Pilcher
2012-08-29 7:56 ` Daniel Vetter [this message]
2012-08-29 19:53 ` Ian Pilcher
2012-08-29 21:38 ` Adam Jackson
2012-08-30 5:23 ` Ian Pilcher
2012-08-30 7:41 ` Daniel Vetter
2012-09-04 14:02 ` Ian Pilcher
2012-09-11 13:59 ` Ian Pilcher
2012-08-28 8:41 ` Baurzhan Ismagulov
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=20120829075616.GA5278@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox