dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95017] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).
Date: Mon, 02 May 2016 15:00:12 +0000	[thread overview]
Message-ID: <bug-95017-502-x5zf39Wjrs@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95017-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 876 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=95017

--- Comment #9 from Ilia Mirkin <imirkin@alum.mit.edu> ---
(In reply to Mathieu Malaterre from comment #8)
> (In reply to Ilia Mirkin from comment #7)
> > FWIW on nouveau we just default agpmode=0 in a #ifdef __powerpc__. Perhaps
> > the same thing can work for radeon.
> 
> Well radeon_agpmode is already set to 0 already[*]. My patch force to
> PCI(-1) when user did not specify any value.
> 
> [*]https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/radeon/
> radeon_drv.c#L173

Oh, the logic is flipped from nouveau... on nouveau, -1 == autodetect and 0 ==
no agp. So in your case, just set it to -1 instead of 0 for powerpc. i.e.

#ifdef __powerpc__
int radeon_agpmode = -1;
#else
int radeon_agpmode = 0;
#endif

or something similar.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1924 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

  parent reply	other threads:[~2016-05-02 15:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-95017-502@http.bugs.freedesktop.org/>
2016-04-19 13:57 ` [Bug 95017] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35) bugzilla-daemon
2016-04-19 13:59 ` bugzilla-daemon
2016-04-20  3:40 ` bugzilla-daemon
2016-05-02 14:31 ` bugzilla-daemon
2016-05-02 14:32 ` bugzilla-daemon
2016-05-02 14:48 ` bugzilla-daemon
2016-05-02 14:55 ` bugzilla-daemon
2016-05-02 15:00 ` bugzilla-daemon [this message]
2016-05-03  7:55 ` bugzilla-daemon
2016-05-03  8:03 ` bugzilla-daemon
2016-05-26  8:54 ` bugzilla-daemon
2016-05-26  8:54 ` bugzilla-daemon
2016-10-10 23:29 ` bugzilla-daemon
2016-10-22 11:30 ` bugzilla-daemon
2016-10-22 11:34 ` bugzilla-daemon
2016-10-24  2:35 ` bugzilla-daemon
2016-10-24  7:26 ` bugzilla-daemon
2018-12-02 23:01 ` bugzilla-daemon
2018-12-02 23:03 ` bugzilla-daemon
2018-12-02 23:07 ` bugzilla-daemon
2018-12-02 23:48 ` bugzilla-daemon
2019-11-19  9:15 ` 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-95017-502-x5zf39Wjrs@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