From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 58660] Radeon HD 6950 completely broken.
Date: Sat, 22 Dec 2012 20:28:48 +0000 [thread overview]
Message-ID: <bug-58660-502-tfeclRTOKi@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58660-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58660
--- Comment #1 from Thomas Rohloff <v10lator@myway.de> ---
Forget to say: This is on newest mesa from git with kernel 3.8-rc1 (+ this
patch:
http://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-fixes-3.8&id=668bbc81baf0f34df832d8aca5c7d5e19a493c68
)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1252 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:[~2012-12-22 20:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 20:28 [Bug 58660] New: Radeon HD 6950 completely broken bugzilla-daemon
2012-12-22 20:28 ` bugzilla-daemon [this message]
2012-12-22 23:49 ` [Bug 58660] Radeon HD 6950 completely broken with sapphire unlocked vbios bugzilla-daemon
2012-12-23 0:21 ` bugzilla-daemon
2012-12-23 0:22 ` bugzilla-daemon
2012-12-23 0:23 ` bugzilla-daemon
2012-12-23 19:24 ` bugzilla-daemon
2012-12-23 21:44 ` bugzilla-daemon
2012-12-24 13:13 ` [Bug 58660] Radeon HD 6950 completely broken with sapphire locked vbios bugzilla-daemon
2014-01-23 15:19 ` [Bug 58660] CAYMAN broken with HyperZ on bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-08-24 13:38 ` bugzilla-daemon
2014-09-01 21:05 ` 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-58660-502-tfeclRTOKi@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