From: Daniel Vetter <daniel@ffwll.ch>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [RFC] drm: add support for tiled/compressed/etc modifier in addfb2
Date: Mon, 15 Dec 2014 08:39:41 +0100 [thread overview]
Message-ID: <20141215073941.GM27182@phenom.ffwll.local> (raw)
In-Reply-To: <CAF6AEGv2ySxY5Nh3+JYP-dCHX1orCHZowm_YOJbk1A9MXDr-+w@mail.gmail.com>
On Fri, Dec 12, 2014 at 10:56:21AM -0500, Rob Clark wrote:
> On Fri, Dec 12, 2014 at 10:11 AM, Daniel Stone <daniel@fooishbar.org> wrote:
> > Hi,
> >
> > On 12 December 2014 at 14:56, Ville Syrjälä <ville.syrjala@linux.intel.com>
> > wrote:
> >>
> >> On Fri, Dec 12, 2014 at 08:50:18AM -0500, Rob Clark wrote:
> >>
> >> > It does make me briefly think of just letting us set properties on fb
> >>
> >> > objects :-P (but maybe that is a bit overkill)
> >>
> >> Yeah I had the same idea at some point. But then I decided that we could
> >> just have these as properties on the plane.
> >
> >
> > Mm, it does seem a bit weird. Yes, they are relative to how the plane
> > interprets things, but then again so is the format surely. Not to mention
> > another thing to go wrong, if someone forgets to set and/or clear it when
> > changing the plane. Keeping it in the fb eliminates that possibility.
> >
>
> yeah.. logically it seems nicer for them to be prop's on fb's. The
> drawback is having to invent some bit of infrastructure to support
> that. Avoidance of inheriting someone else's plane prop's might be
> enough justification to invent that infrastructure. But fb prop's
> don't really help w/ the whole not-all-planes-are-the-same thing..
The nice thing with fbs currently is that all the metadata is invariant.
Imo we should keep that for any prop extension, since it massively
simplifies things for everyone.
But I'm not sure that's so important since we already have (and probably
always will have) a mess between plane and fb props. E.g. the rotation
thing actually affects the pte ordering on skl. So would be nice to have
as an invariant fb prop, but since it's now on the plane we can't change
it.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
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-15 7:39 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 [this message]
2014-12-16 3:56 ` Michel Dänzer
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=20141215073941.GM27182@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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