From: Adam Jackson <ajax@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: -next queue and EDID stuff
Date: Mon, 27 Aug 2012 16:24:02 -0400 [thread overview]
Message-ID: <503BD762.6070204@redhat.com> (raw)
In-Reply-To: <CAPM=9ty5rCTQXGp4t9H6RD2_NEGX0oCbD_7y6HpMOYLnGdyWnA@mail.gmail.com>
On 8/23/12 7:50 PM, Dave Airlie wrote:
> Hi guys (but mainly ajax)
>
> I have a bunch of EDID and quirk stuff outstanding,
>
> I've made a bundle on patchwork for it
> https://patchwork.kernel.org/bundle/airlied/edid-review/
https://patchwork.kernel.org/patch/1364501/ - I'm nervous about this on
non-EDDC monitors, things are touchy enough as it is. Would prefer if
we did the normal 2-message thing for blocks 0 and 1, and only did 3
messages if segment != 0.
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.
For the rest (though I have some complaints that aren't enough to
justify saying no):
Reviewed-by: Adam Jackson <ajax@redhat.com>
Paul's FORCE_REDUCED_BLANKING series makes me nervous about what those
monitors will do over VGA, since from a conversation we had on IRC he
hasn't been able to test that.
I don't really see the point in the EDID_MFG_ID() bit of the quirks
rework. Have we actually seen a monitor where that field was malformed
in a way that would require it?
- ajax
next prev parent reply other threads:[~2012-08-27 20:24 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 [this message]
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
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=503BD762.6070204@redhat.com \
--to=ajax@redhat.com \
--cc=airlied@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