From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Pilcher Subject: Re: -next trees Date: Tue, 25 Sep 2012 13:47:29 -0500 Message-ID: <5061FC41.7080009@gmail.com> References: <505E916F.7000803@gmail.com> <1348497252.15901.46.camel@atropine> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------060900030502050909040903" Return-path: Received: from mail-yx0-f177.google.com (mail-yx0-f177.google.com [209.85.213.177]) by gabe.freedesktop.org (Postfix) with ESMTP id E5C3F9F60E for ; Tue, 25 Sep 2012 11:47:33 -0700 (PDT) Received: by yenr1 with SMTP id r1so836910yen.36 for ; Tue, 25 Sep 2012 11:47:33 -0700 (PDT) In-Reply-To: <1348497252.15901.46.camel@atropine> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Adam Jackson Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org This is a multi-part message in MIME format. --------------060900030502050909040903 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 09/24/2012 09:34 AM, Adam Jackson wrote: > 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? Yes. The DISABLE_INFOFRAMES quirk will still be required by this display. (The reason that the Intel driver got dragged into this is because it is sending audio InfoFrames to the display, even when drm_detect_hdmi_monitor returns false.) > 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. EDID attached. In the meantime, I would like to move the ball forward on this issue. As I see it, there 3 issues that have become conflated: 1. The display (LG L246WP) is confused by *any* InfoFrames. 2. The Intel driver is sending audio InfoFrames when drm_detect_hdmi_monitor returns false and drm_detect_monitor_audio returns true. 3. drm_detect_monitor_audio is returning true for the LG L246WP, which definitely doesn't have any audio capabilities. This may be a bug in the display's EDID, or it may be a parsing error. Would you be amenable to a patch series that addresses *only* issue number 1? Thanks! -- ======================================================================== Ian Pilcher arequipeno@gmail.com "If you're going to shift my paradigm ... at least buy me dinner first." ======================================================================== --------------060900030502050909040903 Content-Type: application/octet-stream; name="edid.bin" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="edid.bin" AP///////wAebT9W01cBAAIRAQOONCB46lrVp1ZLmyQTUFSlSwCpQIGPswCBT4GAAQEBAQEB KDyAoHCwI0AwIDYAsEQRAAAaSD9AMGKwMkBAwBMAsEQRAAAeAAAA/QA4Sx5TEQAKICAgICAg AAAA/ABMMjQ2V1AKICAgICAgAYECAxxxSZAFBAMBHxQSEyMJBweDAQAAZQMMABAAAjqAGHE4 LUBYLEUABkQhAAAeAR2AGHEcFiBYLCUABkQhAACeAR0AclHQHiBuKFUABkQhAAAejArQiiDg LRAQPpYABkQhAAAeAjqA0HI4LUAQLEUgBkQhAAAeAAAAAAAAAAAAvQ== --------------060900030502050909040903 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --------------060900030502050909040903--