From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74347] openra screen corruption on a HD2600
Date: Mon, 03 Feb 2014 03:48:51 +0000 [thread overview]
Message-ID: <bug-74347-502-RDSYk8STr8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74347-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=74347
higuita@gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Drivers/Gallium/r600 |Drivers/DRI/Radeon
--- Comment #2 from higuita@gmx.net ---
with R600_DEBUG=noinvalrange the screen show up fine, without any corruption..
but the game seems slower (but i might be wrong)
So what do i do with this? add to the openra startup script or this was just to
help debuging?
thanks for the help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1855 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:[~2014-02-03 3:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 1:08 [Bug 74347] New: openra screen corruption on a HD2600 bugzilla-daemon
2014-02-02 10:37 ` [Bug 74347] " bugzilla-daemon
2014-02-02 11:55 ` bugzilla-daemon
2014-02-03 3:48 ` bugzilla-daemon [this message]
2014-02-03 12:41 ` bugzilla-daemon
2014-02-03 15:03 ` bugzilla-daemon
2014-02-04 0:11 ` bugzilla-daemon
2014-02-04 17:49 ` bugzilla-daemon
2014-02-04 20:54 ` bugzilla-daemon
2014-02-04 21:52 ` bugzilla-daemon
2014-02-04 21:55 ` bugzilla-daemon
2014-04-24 23:43 ` bugzilla-daemon
2014-05-07 23:40 ` 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-74347-502-RDSYk8STr8@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.