From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60236] New: corruption of text and bottom of screen in xonotic menus since 325422c49449acdd8df1eb2ca8ed81f7696c38cc
Date: Sun, 03 Feb 2013 14:39:17 +0000 [thread overview]
Message-ID: <bug-60236-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=60236
Priority: medium
Bug ID: 60236
Assignee: dri-devel@lists.freedesktop.org
Summary: corruption of text and bottom of screen in xonotic
menus since 325422c49449acdd8df1eb2ca8ed81f7696c38cc
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: pheldens@ziggo.nl
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
bisected to this commit
325422c49449acdd8df1eb2ca8ed81f7696c38cc is the first bad commit
commit 325422c49449acdd8df1eb2ca8ed81f7696c38cc
Author: Jerome Glisse <jglisse@redhat.com>
Date: Mon Jan 7 17:45:59 2013 -0500
r600g: add async for staging buffer upload v2
v2: Add virtual address to dma src/dst offset for cayman
Signed-off-by: Jerome Glisse <jglisse@redhat.com>
:040000 040000 4ef6e784f3acb7f21da0c5e1923810c78917d16d
55f0ce7d9793ce04d392fc7943059545053a9d79 M src
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2589 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 reply other threads:[~2013-02-03 14:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 14:39 bugzilla-daemon [this message]
2013-02-03 14:39 ` [Bug 60236] corruption of text and bottom of screen in xonotic menus since 325422c49449acdd8df1eb2ca8ed81f7696c38cc bugzilla-daemon
2013-02-03 14:41 ` bugzilla-daemon
2013-02-05 11:33 ` bugzilla-daemon
2013-02-05 11:35 ` bugzilla-daemon
2013-02-05 13:36 ` bugzilla-daemon
2013-02-05 13:51 ` bugzilla-daemon
2013-02-05 15:54 ` bugzilla-daemon
2013-02-05 16:19 ` bugzilla-daemon
2013-02-05 16:26 ` bugzilla-daemon
2013-02-05 16:56 ` bugzilla-daemon
2013-02-05 17:01 ` bugzilla-daemon
2013-02-06 20:03 ` bugzilla-daemon
2013-02-06 20:34 ` bugzilla-daemon
2013-02-06 20:44 ` bugzilla-daemon
2013-02-06 20:45 ` bugzilla-daemon
2013-02-06 21:24 ` bugzilla-daemon
2013-02-06 21:31 ` bugzilla-daemon
2013-02-06 21:35 ` bugzilla-daemon
2013-02-06 21:36 ` bugzilla-daemon
2013-02-06 23:41 ` bugzilla-daemon
2013-02-07 7:14 ` bugzilla-daemon
2013-02-07 15:21 ` bugzilla-daemon
2013-02-07 15:44 ` bugzilla-daemon
2013-02-07 18:00 ` bugzilla-daemon
2013-02-07 19:25 ` bugzilla-daemon
2013-02-07 20:02 ` bugzilla-daemon
2013-02-07 21:54 ` bugzilla-daemon
2013-02-07 22:00 ` bugzilla-daemon
2013-02-08 9:58 ` bugzilla-daemon
2013-02-08 13:09 ` bugzilla-daemon
2013-02-08 14:57 ` bugzilla-daemon
2013-02-08 20:25 ` bugzilla-daemon
2013-02-08 20:28 ` bugzilla-daemon
2013-02-08 20:29 ` bugzilla-daemon
2013-02-08 23:40 ` bugzilla-daemon
2013-02-12 18:57 ` bugzilla-daemon
2013-02-19 2:18 ` bugzilla-daemon
2013-02-19 13:34 ` 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-60236-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