From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62578] r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state!
Date: Thu, 21 Mar 2013 21:20:51 +0000 [thread overview]
Message-ID: <bug-62578-502-vAW3qUVSRm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62578-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 547 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62578
--- Comment #8 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #7)
> I filed a bug against kwin. Looks like they will have checks in place in
> 4.11 to not use OpenGL on this hardware. Not sure if anything should still
> be done on the mesa side or not to help with this.
Depending on what features they are using, it should be fine to use GL on this
hardware. They just have to respect the hw limits.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1536 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-03-21 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 21:12 [Bug 62578] New: r300: Implementation error: Render targets are too big in r300_set_framebuffer_state, refusing to bind framebuffer state! bugzilla-daemon
2013-03-20 21:23 ` [Bug 62578] " bugzilla-daemon
2013-03-20 21:49 ` bugzilla-daemon
2013-03-21 13:36 ` bugzilla-daemon
2013-03-21 13:36 ` bugzilla-daemon
2013-03-21 14:12 ` bugzilla-daemon
2013-03-21 14:28 ` bugzilla-daemon
2013-03-21 15:10 ` bugzilla-daemon
2013-03-21 21:15 ` bugzilla-daemon
2013-03-21 21:20 ` bugzilla-daemon [this message]
2019-09-18 18:51 ` 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-62578-502-vAW3qUVSRm@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