dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <snjw23@gmail.com>
To: Marcus Lorentzon <marcus.xm.lorentzon@stericsson.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>
Subject: Re: [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to add multi plane formats
Date: Fri, 06 Apr 2012 22:04:10 +0200	[thread overview]
Message-ID: <4F7F4C3A.6030903@gmail.com> (raw)
In-Reply-To: <4F759482.9090804@stericsson.com>

On 03/30/2012 01:09 PM, Marcus Lorentzon wrote:
> On 03/30/2012 12:12 PM, Ville Syrjälä wrote:
>>> +#define DRM_FORMAT_NV12MT fourcc_code('T', 'M', '1', '2') /* 2x2
>>> subsampled 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.

Just for the record, documentation of this tiled macro-block format
can be found here:

http://linuxtv.org/downloads/v4l-dvb-apis/re27.html

--
Regards,
Sylwester

  reply	other threads:[~2012-04-06 20:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  2:54 [PATCH libdrm] libdrm: update drm/drm_fourcc.h from kernel to add multi plane formats Seung-Woo Kim
2012-03-30 10:12 ` Ville Syrjälä
2012-03-30 11:07   ` 김승우
2012-03-30 12:13     ` Ville Syrjälä
2012-03-30 11:09   ` Marcus Lorentzon
2012-04-06 20:04     ` Sylwester Nawrocki [this message]
2012-04-05 18:13   ` Ville Syrjälä
2012-04-06  0:13     ` Rob Clark
2012-04-06  6:05     ` Inki Dae
2012-04-06  7:43       ` Ville Syrjälä
2012-04-06  9:22         ` Kyungmin Park
2012-04-06 11:22           ` Sylwester Nawrocki
2012-04-07  6:01         ` daeinki

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=4F7F4C3A.6030903@gmail.com \
    --to=snjw23@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=marcus.xm.lorentzon@stericsson.com \
    --cc=sw0312.kim@samsung.com \
    /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