From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91268] R6xx freezes with kernel 3.17 and up
Date: Sun, 12 Jul 2015 12:37:41 +0000 [thread overview]
Message-ID: <bug-91268-502-aEOgyX3ZIy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91268-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1693 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91268
--- Comment #3 from Kajzer <kap3tan@gmail.com> ---
Trouble is that kernel won't compile now.
CC [M] drivers/gpu/drm/radeon/radeon_object.o
drivers/gpu/drm/radeon/radeon_object.c: In function
‘radeon_ttm_placement_from_domain’:
drivers/gpu/drm/radeon/radeon_object.c:117:20: error: ‘RADEON_GEM_GTT_UC’
undeclared (first use in this function)
if (rbo->flags & RADEON_GEM_GTT_UC) {
^
drivers/gpu/drm/radeon/radeon_object.c:117:20: note: each undeclared identifier
is reported only once for each function it appears in
drivers/gpu/drm/radeon/radeon_object.c:119:28: error: ‘RADEON_GEM_GTT_WC’
undeclared (first use in this function)
} else if ((rbo->flags & RADEON_GEM_GTT_WC) ||
^
drivers/gpu/drm/radeon/radeon_object.c: In function ‘radeon_bo_create’:
drivers/gpu/drm/radeon/radeon_object.c:198:18: error: ‘RADEON_GEM_GTT_WC’
undeclared (first use in this function)
bo->flags &= ~(RADEON_GEM_GTT_WC | RADEON_GEM_GTT_UC);
^
drivers/gpu/drm/radeon/radeon_object.c:198:38: error: ‘RADEON_GEM_GTT_UC’
undeclared (first use in this function)
bo->flags &= ~(RADEON_GEM_GTT_WC | RADEON_GEM_GTT_UC);
^
make[5]: *** [drivers/gpu/drm/radeon/radeon_object.o] Error 1
I made a patch with git show 02376d8282b88f07d0716da6155094c8760b1a13 >
badcommit.patch
It patched fine with no errors.
I'm out of moves now, is there any other way to either add this commit to 3.16
or take it out from 3.17 ?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2475 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:[~2015-07-12 12:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:15 [Bug 91268] R6xx freezes with kernel 3.17 and up bugzilla-daemon
2015-07-11 19:20 ` bugzilla-daemon
2015-07-12 2:20 ` bugzilla-daemon
2015-07-12 12:37 ` bugzilla-daemon [this message]
2015-07-13 14:19 ` bugzilla-daemon
2015-07-13 15:30 ` bugzilla-daemon
2015-07-15 3:30 ` bugzilla-daemon
2015-07-15 12:27 ` bugzilla-daemon
2015-07-15 12:29 ` bugzilla-daemon
2015-07-16 3:52 ` bugzilla-daemon
2015-07-16 13:12 ` bugzilla-daemon
2015-07-16 13:56 ` bugzilla-daemon
2015-07-16 13:58 ` bugzilla-daemon
2015-07-16 14:37 ` bugzilla-daemon
2015-07-16 14:43 ` bugzilla-daemon
2015-07-16 14:49 ` bugzilla-daemon
2015-07-16 15:03 ` bugzilla-daemon
2015-07-16 16:15 ` bugzilla-daemon
2015-07-17 3:06 ` bugzilla-daemon
2015-07-17 3:30 ` bugzilla-daemon
2015-07-24 19:38 ` bugzilla-daemon
2015-07-24 19:42 ` bugzilla-daemon
2015-08-04 10:00 ` bugzilla-daemon
2015-08-04 14:33 ` bugzilla-daemon
2015-10-29 20:34 ` bugzilla-daemon
2015-11-26 8:17 ` bugzilla-daemon
2016-01-29 2:42 ` bugzilla-daemon
2016-03-22 15:54 ` 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-91268-502-aEOgyX3ZIy@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