From: Maxime Ripard <mripard@kernel.org>
To: "Jernej Škrabec" <jernej.skrabec@siol.net>
Cc: roman.stratiienko@globallogic.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: drm/sun4i: Add missing pixel formats to the vi layer
Date: Fri, 20 Sep 2019 08:20:20 +0200 [thread overview]
Message-ID: <20190920062020.zyt5ng6cxtu6muye@gilmour> (raw)
In-Reply-To: <9229663.7SG9YZCNdo@jernej-laptop>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Thu, Sep 19, 2019 at 08:53:10PM +0200, Jernej Škrabec wrote:
> Dne sreda, 18. september 2019 ob 13:05:41 CEST je
> roman.stratiienko@globallogic.com napisal(a):
> > From: Roman Stratiienko <roman.stratiienko@globallogic.com>
> >
> > According to Allwinner DE2.0 Specification REV 1.0, vi layer supports the
> > following pixel formats: ABGR_8888, ARGB_8888, BGRA_8888, RGBA_8888
>
> It's true that DE2 VI layers support those formats, but it wouldn't change
> anything because alpha blending is not supported by those planes. These
> formats were deliberately left out because their counterparts without alpha
> exist, for example ABGR8888 <-> XBGR8888. It would also confuse user, which
> would expect that alpha blending works if format with alpha channel is
> selected.
I'm not too familiar with the DE2 code, but why is alpha not working
if the VI planes support formats with alpha?
Thanks!
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-09-20 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 11:05 [PATCH] drm/sun4i: Add missing pixel formats to the vi layer roman.stratiienko
2019-09-19 18:53 ` Jernej Škrabec
2019-09-20 6:20 ` Maxime Ripard [this message]
2019-09-20 10:14 ` Roman Stratiienko
2019-09-20 20:22 ` Roman Stratiienko
2019-09-20 20:31 ` Jernej Škrabec
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=20190920062020.zyt5ng6cxtu6muye@gilmour \
--to=mripard@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.stratiienko@globallogic.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;
as well as URLs for NNTP newsgroup(s).