From: "Michel Dänzer" <michel@daenzer.net>
To: Daniel Stone <daniel@fooishbar.org>, Rob Clark <robdclark@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [RFC] drm: add support for tiled/compressed/etc modifier in addfb2
Date: Tue, 16 Dec 2014 12:56:57 +0900 [thread overview]
Message-ID: <548FAD89.60607@daenzer.net> (raw)
In-Reply-To: <CAPj87rNjtBQiMR70+3jjubX2MzGzUrNyk=6i5Ycg3j9PseWoiQ@mail.gmail.com>
On 12.12.2014 20:27, Daniel Stone wrote:
> On 10 December 2014 at 17:17, Rob Clark <robdclark@gmail.com
> <mailto:robdclark@gmail.com>> wrote:
>
> In DRM/KMS we are lacking a good way to deal with tiled/compressed
> formats. Especially in the case of dmabuf/prime buffer sharing, where
> we cannot always rely on under-the-hood flags passed to driver specific
> gem-create ioctl to pass around these extra flags.
>
> The proposal is to add a per-plane format modifier. This allows to, if
> necessary, use different tiling patters for sub-sampled planes, etc.
> The format modifiers are added at the end of the ioctl struct, so for
> legacy userspace it will be zero padded.
>
>
> Cool, thanks a lot for looking at this! My one comment is that we could
> maybe go even further: keep the current modifier as a strict
> pixel-layout modifier (e.g. tiled, compressed - anything that affects
> how you actually determine pixel location), and then support an extra
> (perhaps non-vendor-namespaced) argument for optional pixel
> _interpretation_ modifiers, e.g. the hints in
> EGL_EXT_image_dma_buf_import. V4L2 is starting to properly attack things
> like chroma siting, and being able to specify narrow/wide YUV range is
> pretty important for STB/DTV in particular. And they're actually
> starting to move to KMS, too ...
>
> It might be useful to make the interpretation modifiers bitmaskable, so
> they can be combined (e.g. wide-range/unclamped YUV | whatever chroma
> siting), but I can't think of a usecase for combining multiple layout
> modifiers (e.g. this tiling | that compression).
I might be misunderstanding what you're referring to, but FWIW: With AMD
GPUs, the compression format and tiling parameters can be chosen
(mostly) independently.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-12-16 3:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:17 [RFC] drm: add support for tiled/compressed/etc modifier in addfb2 Rob Clark
2014-12-10 17:30 ` Daniel Vetter
2014-12-12 20:56 ` Laurent Pinchart
2014-12-15 7:33 ` Daniel Vetter
2014-12-18 20:54 ` Laurent Pinchart
2014-12-18 21:22 ` Daniel Vetter
2014-12-19 0:55 ` Rob Clark
2014-12-20 19:04 ` Laurent Pinchart
2014-12-12 11:27 ` Daniel Stone
2014-12-12 13:50 ` Rob Clark
2014-12-12 14:56 ` Ville Syrjälä
2014-12-12 15:11 ` Daniel Stone
2014-12-12 15:30 ` Ville Syrjälä
2014-12-12 16:00 ` Rob Clark
2014-12-12 16:14 ` Ville Syrjälä
2014-12-12 17:05 ` Rob Clark
2014-12-15 7:42 ` Daniel Vetter
2014-12-12 17:11 ` Daniel Stone
2014-12-12 18:00 ` Ville Syrjälä
2014-12-12 18:05 ` Daniel Stone
2014-12-12 18:22 ` Ville Syrjälä
2014-12-15 22:19 ` Daniel Stone
2014-12-16 14:42 ` Ville Syrjälä
2014-12-12 15:56 ` Rob Clark
2014-12-15 7:39 ` Daniel Vetter
2014-12-16 3:56 ` Michel Dänzer [this message]
2014-12-16 8:01 ` Daniel Stone
2014-12-16 14:20 ` Rob Clark
2014-12-12 20:57 ` Laurent Pinchart
2014-12-12 21:33 ` Rob Clark
2014-12-13 20:30 ` Ville Syrjälä
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=548FAD89.60607@daenzer.net \
--to=michel@daenzer.net \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=robdclark@gmail.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