From: Adam Jackson <ajax@redhat.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: -next queue and EDID stuff
Date: Tue, 28 Aug 2012 20:13:45 -0400 [thread overview]
Message-ID: <503D5EB9.2040405@redhat.com> (raw)
In-Reply-To: <503D553C.9000503@gmail.com>
On 8/28/12 7:33 PM, Ian Pilcher wrote:
> On 08/27/2012 03:24 PM, Adam Jackson wrote:
>> https://patchwork.kernel.org/patch/1310091/ - nak, the commit message
>> itself gives away that we're doing else something wrong here. If
>> DISABLE_AUDIO is sufficient for one driver it should be sufficient for all.
>
> 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.
- ajax
next prev parent reply other threads:[~2012-08-29 0:13 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 [this message]
2012-08-29 4:18 ` Ian Pilcher
2012-08-29 7:56 ` Daniel Vetter
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=503D5EB9.2040405@redhat.com \
--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.