From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106601] The internal format RGB32F should be color-renderable for texture, But mesa can not support it
Date: Thu, 24 May 2018 06:08:12 +0000 [thread overview]
Message-ID: <bug-106601-502-QiRFC2FvCw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106601-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1830 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #12 from Yunchao He <yunchao.he@intel.com> ---
(In reply to Ilia Mirkin from comment #9)
> "Color-renderable" means "is it legal to use this format". It does NOT mean
> "the driver allows rendering to this format".
I am not a driver expert. But my understanding is that color-renderable means
that we can render into this format as a color buffer. If color-renderable
means "is it legal to use this format", then I can't explain these two
questions as follows:
1. why we need to list that format which is illegal to use at all in spec? I
suppose there are many formats for graphics/video. Enumerating formats that are
not useful for texture (or renderbuffer) seems to be weird.
2. If color-renderable(or renderable) means that "is it legal to use this
format" for a texture. Then that format is not allow to sample from. If so, how
to distinguish these two kinds of formats: 1) some formats can be supported by
a texture to sample only, they can't be used to render into as a render target
via fbo, 2) some other formats can be supported by a texture to sample, and
render into as well.
The statement that "Color-renderable means is it legal to use this format. It
does NOT mean the driver allows rendering to this format" is correct for a
renderbuffer, but I think it is incorrect for a texture. Because a renderbuffer
is only used to render into, they can't be used to sample from. But this issue
is talking about texture, NOT renderbuffer. Maybe for the underlying
implementation, both texture and renderbuffer are mapped into the same GPU
memory (or even CPU memory), but from the perspective of users, texture and
renderbuffer are quite different.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2837 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-24 6:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 5:39 [Bug 106601] angle_end2end_test Texture2DTest.CopySubImageFloat_RGB_RGB/ES2_OPENGL fails bugzilla-daemon
2018-05-22 6:09 ` bugzilla-daemon
2018-05-22 6:12 ` bugzilla-daemon
2018-05-22 6:16 ` [Bug 106601] The internal format RGB32F is not color-renderable, this is not in accordance with Opengl 3.0 spec bugzilla-daemon
2018-05-22 6:16 ` [Bug 106601] The internal format RGB32F is not color-renderable, This " bugzilla-daemon
2018-05-22 6:22 ` bugzilla-daemon
2018-05-22 6:36 ` bugzilla-daemon
2018-05-22 13:23 ` bugzilla-daemon
2018-05-23 5:01 ` bugzilla-daemon
2018-05-23 6:09 ` bugzilla-daemon
2018-05-23 15:52 ` bugzilla-daemon
2018-05-24 1:46 ` [Bug 106601] The internal format RGB32F should be color-renderable for texture, But mesa can not support it bugzilla-daemon
2018-05-24 2:37 ` bugzilla-daemon
2018-05-24 5:43 ` bugzilla-daemon
2018-05-24 5:53 ` bugzilla-daemon
2018-05-24 6:08 ` bugzilla-daemon [this message]
2018-05-24 6:24 ` bugzilla-daemon
2018-10-12 7:12 ` bugzilla-daemon
2019-09-18 19:41 ` bugzilla-daemon
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=bug-106601-502-QiRFC2FvCw@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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).