All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Qiang Yu <yuq825@gmail.com>
Cc: lima@lists.freedesktop.org,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	David Airlie <airlied@linux.ie>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH v2] drm/fourcc: add ARM GPU tile format
Date: Sat, 9 Mar 2019 18:53:37 -0800	[thread overview]
Message-ID: <20190310025337.GA2118@rosenzweig.io> (raw)
In-Reply-To: <CAKGbVbshsMPxLrs792SctXbKETS60t-M6MYB2G9qbmqZF4BvtA@mail.gmail.com>

> If you think Midgard/Bifrost is compatible with AFBC and don't have it's
> own format, and name "device" is improper,  I can rename
> DRM_FORMAT_MOD_ARM_DEVICE_AFBC to DRM_FORMAT_MOD_ARM_TYPE_AFBC
> DRM_FORMAT_MOD_ARM_DEVICE_GPU to DRM_FORMAT_MOD_ARM_TYPE_UTGARD

That name is misleading, too. Midgard/Bifrost is compatible with *both*
AFBC *and* tiled formats.

> Yes, lima need this when xserver/client share window buffer. Client may
> render into a tiled window buffer to be presented to xserver, so need a
> modifier to describe the buffer format. And Utgard can render into both
> tiled and linear buffers.

I see. I didn't realize Utgard could render into tiled formats; that's
nice :)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-03-10  2:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 14:09 [PATCH v2] drm/fourcc: add ARM GPU tile format Qiang Yu
2019-03-10  2:08 ` Alyssa Rosenzweig
2019-03-10  2:35   ` Qiang Yu
2019-03-10  2:53     ` Alyssa Rosenzweig [this message]
2019-03-10  3:01       ` Qiang Yu
2019-03-10  3:04         ` Alyssa Rosenzweig
2019-03-11 16:00 ` Ayan Halder
2019-03-11 16:39   ` Alyssa Rosenzweig
2019-03-12  1:50     ` Qiang Yu
2019-03-12 15:41     ` Ayan Halder
2019-03-13 13:16       ` Qiang Yu
2019-03-14 22:58         ` Alyssa Rosenzweig
2019-03-14 22:54       ` Alyssa Rosenzweig

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=20190310025337.GA2118@rosenzweig.io \
    --to=alyssa@rosenzweig.io \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lima@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=sean@poorly.run \
    --cc=yuq825@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.