From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Jackson Subject: Re: [PATCH] drm: parse color format support for digital displays Date: Fri, 15 Apr 2011 15:36:22 -0400 Message-ID: <4DA89E36.2040803@redhat.com> References: <1302892813-4529-1-git-send-email-jbarnes@virtuousgeek.org> <4DA898BE.90506@redhat.com> <20110415121931.42a24970@jbarnes-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by gabe.freedesktop.org (Postfix) with ESMTP id 095359E758 for ; Fri, 15 Apr 2011 12:36:23 -0700 (PDT) In-Reply-To: <20110415121931.42a24970@jbarnes-desktop> 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: Jesse Barnes Cc: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org On 4/15/11 3:19 PM, Jesse Barnes wrote: > Or is there a CEA block extension that allows for more granularity? CEA has bits for the two YCbCr formats too, which we should also parse since there's plenty of 1.3+CEA blocks in the world thanks to HDMI. For CEA blocks version 2 and up (version number in byte 2 of the CEA block, zero-based indexing), (1 << 5) of byte 3 is 4:4:4 and (1 << 4) is 4:2:2. Same byte as what we already check for EDID_BASIC_AUDIO, if that's any clearer. CEA spec contains the same language about always supporting RGB though. I don't have a good answer for what to do if you have a 1.4+CEA block and the two bitfields are inconsistent, besides violence against the monitor vendor. - ajax