From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39287] New: Framebuffer object extension is exposed, but appears never supported by radeon on R200
Date: Sat, 16 Jul 2011 12:07:32 -0700 (PDT) [thread overview]
Message-ID: <bug-39287-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=39287
Summary: Framebuffer object extension is exposed, but appears
never supported by radeon on R200
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: b7.10110111@gmail.com
Created an attachment (id=49182)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49182)
Test program
See test program.
A framebuffer object is created there, and a color attachment of 2^n x 2^m is
attached to it. Regardless of using depth renderbuffer attachment, framebuffer
status is always GL_FRAMEBUFFER_UNSUPPORTED. Test program continues execution
nonetheless, to see if something is drawn. In some circumstances, i do see some
part of the image for several frames, but they disappear after that.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-07-16 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 19:07 bugzilla-daemon [this message]
2011-07-16 19:08 ` [Bug 39287] Framebuffer object extension is exposed, but appears never supported by radeon on R200 bugzilla-daemon
2011-07-17 19:51 ` bugzilla-daemon
2015-12-01 0:00 ` 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-39287-502@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