From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28426] hardware cursor corruption with radeon+kms
Date: Thu, 03 Nov 2011 07:25:59 +0000 [thread overview]
Message-ID: <bug-28426-502-Ji4VX66phD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-28426-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=28426
--- Comment #10 from Jürg Billeter <j@bitron.ch> 2011-11-03 00:25:59 PDT ---
I've now updated to Linux 3.1. It's looking fine so far but it usually takes a
couple days or so until the cursor corruption starts. I will report back.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-11-03 7:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 16:16 [Bug 28426] New: hardware cursor corruption with radeon+kms bugzilla-daemon
2010-06-07 16:20 ` [Bug 28426] " bugzilla-daemon
2010-06-07 16:20 ` bugzilla-daemon
2010-06-07 16:21 ` bugzilla-daemon
2010-06-07 16:21 ` bugzilla-daemon
2010-08-09 17:52 ` bugzilla-daemon
2011-08-17 10:06 ` bugzilla-daemon
2011-11-02 7:50 ` bugzilla-daemon
2011-11-02 10:53 ` bugzilla-daemon
2011-11-02 19:39 ` bugzilla-daemon
2011-11-03 7:25 ` bugzilla-daemon [this message]
2011-11-09 16:51 ` bugzilla-daemon
2011-11-10 8:24 ` bugzilla-daemon
2011-11-10 17:46 ` bugzilla-daemon
2012-01-26 13:39 ` bugzilla-daemon
2012-01-26 14:21 ` bugzilla-daemon
2012-01-30 15:41 ` bugzilla-daemon
2019-11-19 8:13 ` 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-28426-502-Ji4VX66phD@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