From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcus Lorentzon <marcus.xm.lorentzon@stericsson.com>
Subject: Re: [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to
	add multi plane formats
Date: Fri, 30 Mar 2012 13:09:54 +0200
Message-ID: <4F759482.9090804@stericsson.com>
References: <1333076090-28881-1-git-send-email-sw0312.kim@samsung.com>
	<20120330101258.GV4917@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from eu1sys200aog111.obsmtp.com (eu1sys200aog111.obsmtp.com
	[207.126.144.131])
	by gabe.freedesktop.org (Postfix) with ESMTP id DE6729E7A7
	for <dri-devel@lists.freedesktop.org>;
	Fri, 30 Mar 2012 04:10:00 -0700 (PDT)
In-Reply-To: <20120330101258.GV4917@intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=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: =?ISO-8859-1?Q?Ville_Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
Cc: "inki.dae@samsung.com" <inki.dae@samsung.com>, "kyungmin.park@samsung.com" <kyungmin.park@samsung.com>, Seung-Woo Kim <sw0312.kim@samsung.com>, "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
List-Id: dri-devel@lists.freedesktop.org

On 03/30/2012 12:12 PM, Ville Syrj=E4l=E4 wrote:
>> +#define DRM_FORMAT_NV12MT	fourcc_code('T', 'M', '1', '2') /* 2x2 subsam=
pled Cr:Cb plane 64x32 macroblocks */
> This one is more difficult. Until now tiling was always handled in
> driver specific manner. OTOH if this format is really supported by
> different devices from multiple vendors, then it would probably
> make sense to add it as a standard format.
>
What about adding a DRM_FORMAT_PRIV_NV12MT and force vendor to add =

detailed documentation about this new format. Because if the format is =

not defined and documented, how will we ever discover if vendors have =

similar formats? And if we document all these MB formats "everyone" =

uses, then maybe we can get HW vendors to unify on a de facto standard. =

It would be nice to have an efficient format supported by everyone, =

instead of having to fallback to old linear formats every time you =

interact with another device.

/BR
/Marcus