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:24:04 +0000 [thread overview]
Message-ID: <bug-106601-502-oaN0bfUghE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106601-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2270 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #13 from Yunchao He <yunchao.he@intel.com> ---
(In reply to Tapani Pälli from comment #11)
> (In reply to Yunchao He from comment #10)
> > (In reply to Tapani Pälli from comment #8)
> > > What comes to conformance, you should refer to latest OpenGL spec (now being
> > > 4.6). In this case you want to render to RGB32F we should take a look at
> > > section "9.2.5 Required Renderbuffer Formats". Since you are using a sized
> > > format, it means you need to check if driver is required to support this
> > > from column 'Req. rend" as said in 9.2.5.
> > >
> > > That said, IMO this bug should be considered a feature request (which is
> > > fine) rather than a missing feature.
> >
> > Sorry. Maybe the description is not clear. The issue we raised is to render
> > into a RGB32F format texture, not RGB32F format renderbuffer.
> >
> > For the latest OpenGL 4.6 spec, RGB32F internalformat is required by
> > texture, see Table 8.12 in GL 4.6 spec. So I think it is a missing feature
> > in mesa for Intel devices.
>
> 'Req. tex.' column in that table means that texture mapping with this format
> should work (sample from in a shader), it does *not* mean that rendering to
> such format should work, for that there is column 'Req. rend.'.
Sorry, I didn't state this clearly. "Req. tex' column in Table 8.12 do means
that texture mapping with this format should work (sample from in a shader),
but whether we can render into such a format depends on "CR" column. CR is an
abbreviation of color-renderable, I think. And corresponding section about "CR"
at 9.4 "Framebuffer Completeness" do talk about rendering into such a texture
as a render target. And section 9.4 also states that it is valid to render into
such a texture (RGB32F).
While "Req. rend" column means whether a format is required by a renderbuffer.
So, according to Table 8.12, RGB32F should be used as a color buffer via fbo in
latest GL 4.6 spec. When we attach a texture with RGB32F internal format to fbo
as color attachment, generating "framebuffer incomplete" in mesa for Intel
devices is incorrect.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3498 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:24 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
2018-05-24 6:24 ` bugzilla-daemon [this message]
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-oaN0bfUghE@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).