From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66932] Screen corruption on Cayman with dpm enabled
Date: Wed, 17 Jul 2013 17:55:43 +0000 [thread overview]
Message-ID: <bug-66932-502-M52Qd2lKIO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66932-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 723 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66932
--- Comment #21 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #19)
> I wasn't very clear in my #12 comment, but what I was trying to say it is
> something fishy about "reg_block->asRegIndexBuf". It is defined in
> atombios.h as:
> ATOM_MEMORY_SETTING_DATA_BLOCK asRegDataBuf[1];
>
It's a variably sized array and the size varies depending on the system. The
size of that array is defined by usRegIndexTblSize. Hence the calculation to
determine the number of elements:
num_entries = (u8)((le16_to_cpu(reg_block->usRegIndexTblSize)) /
sizeof(ATOM_INIT_REG_INDEX_FORMAT)) - 1;
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1582 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:[~2013-07-17 17:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 15:45 [Bug 66932] New: Screen corruption on Cayman with dpm enabled bugzilla-daemon
2013-07-15 15:54 ` [Bug 66932] " bugzilla-daemon
2013-07-16 1:05 ` bugzilla-daemon
2013-07-16 5:11 ` bugzilla-daemon
2013-07-16 13:21 ` bugzilla-daemon
2013-07-16 17:10 ` bugzilla-daemon
2013-07-16 20:43 ` bugzilla-daemon
2013-07-16 20:47 ` bugzilla-daemon
2013-07-16 21:10 ` bugzilla-daemon
2013-07-16 21:23 ` bugzilla-daemon
2013-07-17 1:45 ` bugzilla-daemon
2013-07-17 9:13 ` bugzilla-daemon
2013-07-17 11:09 ` bugzilla-daemon
2013-07-17 16:40 ` bugzilla-daemon
2013-07-17 16:42 ` bugzilla-daemon
2013-07-17 16:48 ` bugzilla-daemon
2013-07-17 17:02 ` bugzilla-daemon
2013-07-17 17:13 ` bugzilla-daemon
2013-07-17 17:47 ` bugzilla-daemon
2013-07-17 17:49 ` bugzilla-daemon
2013-07-17 17:52 ` bugzilla-daemon
2013-07-17 17:55 ` bugzilla-daemon [this message]
2013-07-17 18:00 ` bugzilla-daemon
2013-07-17 18:02 ` bugzilla-daemon
2013-07-17 18:10 ` bugzilla-daemon
2013-07-17 18:14 ` bugzilla-daemon
2013-07-17 18:15 ` bugzilla-daemon
2013-07-17 18:16 ` bugzilla-daemon
2013-07-17 18:25 ` bugzilla-daemon
2013-07-17 20:38 ` bugzilla-daemon
2013-07-17 20:46 ` bugzilla-daemon
2013-07-17 21:42 ` bugzilla-daemon
2013-07-17 21:52 ` bugzilla-daemon
2013-08-13 23:09 ` 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-66932-502-M52Qd2lKIO@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.