From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94025] [bisected] r600_texture.c:562: r600_texture_get_htile_size: Assertion `0' failed
Date: Sat, 06 Feb 2016 18:03:44 +0000 [thread overview]
Message-ID: <bug-94025-502-TrMsfBbDWE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-94025-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 859 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=94025
--- Comment #1 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
I added a line to output the value of "num_pipes" when it can't be matched to
the defined values in the switch:
fprintf(stderr, "Driver was unable to determine num_pipes (value = %i)\n",
num_pipes);
I ended up outputting "Driver was unable to determine num_pipes (value = 12)",
which is not coverded in the switch... Expected?
In commit 294ec530, r600_get_gb_tiling_config() was removed. num_pipes was
defined there and a comment was telling:
"/* Convert Sea Islands register values GB_ADDR_CFG and MC_ADDR_CFG
* into GB_TILING_CONFIG register which is only present on R600-R700. */"
I'm using and R9 290X, which is a Sea Islands, covered by this comment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1739 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-02-06 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 17:46 [Bug 94025] [bisected] r600_texture.c:562: r600_texture_get_htile_size: Assertion `0' failed bugzilla-daemon
2016-02-06 18:03 ` bugzilla-daemon [this message]
2016-02-06 23:30 ` bugzilla-daemon
2016-02-07 6:52 ` bugzilla-daemon
2016-02-07 15:14 ` bugzilla-daemon
2016-02-07 16:04 ` bugzilla-daemon
2016-02-07 16:11 ` 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-94025-502-TrMsfBbDWE@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).