From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56139] [bisected] kernel 3.7.0-rc1 breaks 6950 (CAYMAN)
Date: Mon, 05 Nov 2012 14:03:53 +0000 [thread overview]
Message-ID: <bug-56139-502-21MWp32aTS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56139-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=56139
--- Comment #12 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #11)
> Found what is wrong with the help of a few printk and by comparing to the
> code being replaced. All the logic is good (going through crtc, disabling
> them, waiting for vblank) BUT setting "tmp |=
> EVERGREEN_CRTC_DISP_READ_REQUEST_DISABLE;" is wrong.
>
> If I do as in the previous code by setting tmp = 0 and then continuing with:
> radeon_wait_for_vblank(rdev, i);
> WREG32(EVERGREEN_CRTC_CONTROL + crtc_offsets[i], tmp);
> everything works fine as before.
>
> What is expected from "tmp |= EVERGREEN_CRTC_DISP_READ_REQUEST_DISABLE;"?
> From what I read with printk, it is far from a 0 or a 1. Is this normal?
That's the most important bit in the entire sequence. It's a bit field in a
register (bit 24 to be exact). That bit is the bit that actually disables the
requests from the display controller in the memory controller. The whole point
of this code is to disable all clients of the memory controller (mc_stop()) so
that we can change the location of vram within the GPU's address space. Once
we've moved vram, we can re-enable the clients (mc_resume()) so that they point
to the new vram location.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2220 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-11-05 14:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 13:48 [Bug 56139] New: [bisected] kernel 3.7.0-rc1 breaks 6950 (CAYMAN) bugzilla-daemon
2012-10-18 13:51 ` [Bug 56139] " bugzilla-daemon
2012-10-18 14:16 ` bugzilla-daemon
2012-10-18 23:46 ` bugzilla-daemon
2012-10-22 5:57 ` bugzilla-daemon
2012-10-26 3:17 ` bugzilla-daemon
2012-10-26 14:08 ` bugzilla-daemon
2012-10-27 4:51 ` bugzilla-daemon
2012-10-31 18:29 ` bugzilla-daemon
2012-10-31 19:13 ` bugzilla-daemon
2012-11-01 0:38 ` bugzilla-daemon
2012-11-01 5:30 ` bugzilla-daemon
2012-11-05 6:58 ` bugzilla-daemon
2012-11-05 14:03 ` bugzilla-daemon [this message]
2012-11-05 14:28 ` bugzilla-daemon
2012-11-05 14:55 ` bugzilla-daemon
2012-11-05 16:20 ` bugzilla-daemon
2012-11-05 16:34 ` bugzilla-daemon
2012-11-05 22:46 ` bugzilla-daemon
2012-11-06 0:33 ` bugzilla-daemon
2012-11-06 1:02 ` bugzilla-daemon
2012-11-06 22:32 ` bugzilla-daemon
2012-11-06 22:50 ` bugzilla-daemon
2012-11-06 22:55 ` bugzilla-daemon
2012-11-06 22:56 ` bugzilla-daemon
2012-11-06 22:59 ` bugzilla-daemon
2012-11-11 18:55 ` bugzilla-daemon
2013-04-17 9:11 ` Huacai Chen
2012-11-12 4:04 ` [Bug 56139] [bisected] kernel 3.7.0-rc1 breaks 6950 (boot/grub2 and suspend/resume) (CAYMAN) bugzilla-daemon
2012-11-12 4:27 ` bugzilla-daemon
2012-11-12 5:32 ` bugzilla-daemon
2012-11-12 23:31 ` bugzilla-daemon
2012-11-13 15:15 ` bugzilla-daemon
2012-11-13 15:45 ` bugzilla-daemon
2012-11-14 16:14 ` bugzilla-daemon
2012-11-18 17:05 ` bugzilla-daemon
2012-11-18 19:04 ` bugzilla-daemon
2012-11-18 19:40 ` bugzilla-daemon
2012-11-18 19:41 ` bugzilla-daemon
2012-11-19 14:05 ` bugzilla-daemon
2012-11-19 14:18 ` bugzilla-daemon
2012-11-19 14:19 ` bugzilla-daemon
2012-11-19 23:31 ` bugzilla-daemon
2012-11-20 6:08 ` bugzilla-daemon
2012-11-20 15:23 ` bugzilla-daemon
2012-11-28 6:44 ` bugzilla-daemon
2012-11-28 14:29 ` bugzilla-daemon
2012-11-28 17:08 ` bugzilla-daemon
2013-01-05 5:57 ` bugzilla-daemon
2013-01-31 0:52 ` bugzilla-daemon
2013-01-31 13:35 ` bugzilla-daemon
2013-02-20 5:34 ` bugzilla-daemon
2013-02-23 10:28 ` bugzilla-daemon
2013-02-24 3:21 ` bugzilla-daemon
2013-02-25 1:56 ` bugzilla-daemon
2013-02-25 13:57 ` bugzilla-daemon
2013-03-11 4:41 ` bugzilla-daemon
2013-03-11 4:51 ` bugzilla-daemon
2013-03-11 13:38 ` 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-56139-502-21MWp32aTS@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;
as well as URLs for NNTP newsgroup(s).