From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106601] The internal format RGB32F is not color-renderable, This is not in accordance with Opengl 3.0 spec
Date: Tue, 22 May 2018 06:22:31 +0000 [thread overview]
Message-ID: <bug-106601-502-WabsIRpnYp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106601-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1081 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106601
--- Comment #3 from wangjingbin <jingbin.wang@intel.com> ---
Produce steps:
1. Attached file is the C source code;
2. Build the source file(I built it on Ubuntu 17.04, Intel® HD Graphics
(KabyLake 3x8 GT2)), "gcc -o copySubImageFloatRGB copySubImageFloatRGB.c -lX11
-lepoxy";
3. run "./copySubImageFloatRGB", will print message as follow:
Visual 0xb9 selected
Render: Mesa DRI Intel(R) HD Graphics 630 (Kaby Lake GT2)
Version: 3.0 Mesa 17.1.4
233 glCheckFramebufferStatus error no = 0x8cdd.
The error is result from that the FBO is not completeness when the internal
format of attached image is RGB32F. In another word, The internal format RGB32F
is not color-renderable.
According to GL 3.0 Spec description, Section 4.4 page 291 and Table 3.16 Page
184, The internal format RGB32F is color-renderable
In additional, I have run this test application on Nvidia graphic, it work
successfully
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1984 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-22 6:22 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 [this message]
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
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-WabsIRpnYp@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 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.