From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96423] radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref]
Date: Tue, 07 Jun 2016 12:25:25 +0000 [thread overview]
Message-ID: <bug-96423-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1353 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96423
Bug ID: 96423
Summary: radeonfb: BAR 0: can't reserve [mem
0x98000000-0x9fffffff pref]
Product: DRI
Version: XOrg git
Hardware: PowerPC
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: mathieu.malaterre@gmail.com
On a PowerPC machine, when Open Firmware Frame Buffer is used (OFfb), I
cannot `modprobe radeonfb` (but I can load `radeon`). It currently fails with:
[ 96.551486] radeonfb 0000:00:10.0: enabling device (0006 -> 0007)
[ 96.551526] radeonfb 0000:00:10.0: BAR 0: can't reserve [mem
0x98000000-0x9fffffff pref]
[ 96.551531] radeonfb (0000:00:10.0): cannot request region 0.
[ 96.551545] radeonfb: probe of 0000:00:10.0 failed with error -16
It seems (to me) that it should be possible to add something like this
to `radeonfb`:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/radeon/radeon_drv.c#L353
[...]
/* Get rid of things like offb */
ret = radeon_kick_out_firmware_fb(pdev);
if (ret)
[...]
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2747 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 reply other threads:[~2016-06-07 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 12:25 bugzilla-daemon [this message]
2016-06-07 13:45 ` [Bug 96423] radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref] 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-96423-502@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