From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194761] amdgpu driver breaks on Oland (SI)
Date: Mon, 26 Jun 2017 07:30:34 +0000 [thread overview]
Message-ID: <bug-194761-2300-qoZ4qzY9Ep@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194761
Jean Delvare (jdelvare@suse.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #67 from Jean Delvare (jdelvare@suse.de) ---
We are still waiting for someone at AMD to contact their hardware documentation
team to clarify what Oland64 and Oland128 refer to, and to explain how the
Windows driver can possibly use the P2 tile table for all Oland parts (comment
#60) when the hardware documentation claims some of them must use the P4_8x16
tile table (comment #23) and experiments with the Linux driver confirms this is
the case (comment #26, comment #64.)
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-06-26 7:30 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 8:57 [Bug 194761] New: amdgpu driver breaks on Oland (SI) bugzilla-daemon
2017-03-02 9:37 ` [Bug 194761] " bugzilla-daemon
2017-03-02 15:12 ` bugzilla-daemon
2017-03-02 16:16 ` bugzilla-daemon
2017-03-02 16:23 ` bugzilla-daemon
2017-03-02 16:24 ` bugzilla-daemon
2017-03-02 17:23 ` bugzilla-daemon
2017-03-15 11:30 ` bugzilla-daemon
2017-03-15 11:30 ` bugzilla-daemon
2017-05-19 6:16 ` bugzilla-daemon
2017-05-19 6:35 ` bugzilla-daemon
2017-05-19 9:43 ` bugzilla-daemon
2017-05-19 12:45 ` bugzilla-daemon
2017-05-22 2:32 ` bugzilla-daemon
2017-05-22 9:26 ` bugzilla-daemon
2017-05-22 9:34 ` bugzilla-daemon
2017-05-22 20:57 ` bugzilla-daemon
2017-05-23 14:58 ` bugzilla-daemon
2017-05-24 9:56 ` bugzilla-daemon
2017-05-24 11:49 ` bugzilla-daemon
2017-05-24 12:55 ` bugzilla-daemon
2017-05-26 2:05 ` bugzilla-daemon
2017-05-26 8:06 ` bugzilla-daemon
2017-05-26 8:25 ` bugzilla-daemon
2017-05-26 15:00 ` bugzilla-daemon
2017-05-26 16:38 ` bugzilla-daemon
2017-05-30 9:02 ` bugzilla-daemon
2017-05-30 13:19 ` bugzilla-daemon
2017-05-30 13:59 ` bugzilla-daemon
2017-05-30 14:41 ` bugzilla-daemon
2017-05-31 11:35 ` bugzilla-daemon
2017-06-01 11:53 ` bugzilla-daemon
2017-06-01 20:04 ` bugzilla-daemon
2017-06-02 2:28 ` bugzilla-daemon
2017-06-02 16:18 ` bugzilla-daemon
2017-06-02 20:26 ` bugzilla-daemon
2017-06-02 20:35 ` bugzilla-daemon
2017-06-03 10:27 ` bugzilla-daemon
2017-06-03 10:34 ` bugzilla-daemon
2017-06-03 10:37 ` bugzilla-daemon
2017-06-09 13:33 ` bugzilla-daemon
2017-06-09 13:45 ` bugzilla-daemon
2017-06-09 14:25 ` bugzilla-daemon
2017-06-09 14:28 ` bugzilla-daemon
2017-06-09 14:34 ` bugzilla-daemon
2017-06-09 15:06 ` bugzilla-daemon
2017-06-09 16:59 ` bugzilla-daemon
2017-06-09 17:37 ` bugzilla-daemon
2017-06-09 17:37 ` bugzilla-daemon
2017-06-09 18:40 ` bugzilla-daemon
2017-06-09 18:46 ` bugzilla-daemon
2017-06-09 18:46 ` bugzilla-daemon
2017-06-09 18:51 ` bugzilla-daemon
2017-06-09 18:57 ` bugzilla-daemon
2017-06-09 19:06 ` bugzilla-daemon
2017-06-09 19:08 ` bugzilla-daemon
2017-06-09 19:10 ` bugzilla-daemon
2017-06-09 19:11 ` bugzilla-daemon
2017-06-09 19:13 ` bugzilla-daemon
2017-06-09 19:17 ` bugzilla-daemon
2017-06-09 19:46 ` bugzilla-daemon
2017-06-09 19:52 ` bugzilla-daemon
2017-06-12 7:26 ` bugzilla-daemon
2017-06-12 7:39 ` bugzilla-daemon
2017-06-12 7:40 ` bugzilla-daemon
2017-06-12 7:40 ` bugzilla-daemon
2017-06-12 10:47 ` bugzilla-daemon
2017-06-12 11:09 ` bugzilla-daemon
2017-06-12 13:09 ` bugzilla-daemon
2017-06-15 14:12 ` bugzilla-daemon
2017-06-26 7:30 ` bugzilla-daemon [this message]
2017-06-26 12:30 ` bugzilla-daemon
2017-07-03 14:37 ` bugzilla-daemon
2017-07-03 15:04 ` bugzilla-daemon
2017-07-03 15:11 ` bugzilla-daemon
2017-07-06 15:35 ` bugzilla-daemon
2017-07-06 16:00 ` bugzilla-daemon
2017-07-07 22:12 ` bugzilla-daemon
2017-07-25 13:10 ` bugzilla-daemon
2017-07-28 9:06 ` bugzilla-daemon
2017-07-28 9:26 ` bugzilla-daemon
2017-07-28 14:16 ` bugzilla-daemon
2017-07-28 14:28 ` bugzilla-daemon
2017-07-28 14:31 ` bugzilla-daemon
2017-07-28 14:32 ` bugzilla-daemon
2017-07-28 17:00 ` bugzilla-daemon
2017-07-30 6:21 ` bugzilla-daemon
2017-07-31 14:17 ` bugzilla-daemon
2017-08-01 5:42 ` bugzilla-daemon
2017-08-23 14:47 ` bugzilla-daemon
2017-09-04 8:11 ` bugzilla-daemon
2017-09-11 15:39 ` bugzilla-daemon
2017-10-03 7:26 ` bugzilla-daemon
2017-10-20 14:26 ` bugzilla-daemon
2017-10-20 14:30 ` bugzilla-daemon
2017-10-20 19:20 ` bugzilla-daemon
2017-10-23 11:07 ` 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-194761-2300-qoZ4qzY9Ep@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).