Bug 119741 - radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref]
Summary: radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref]
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(Other) (show other bugs)
Hardware: PPC-32 Linux
: P1 normal
Assignee: drivers_video-other
URL: https://lists.ozlabs.org/pipermail/li...
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-07 13:48 UTC by Mathieu Malaterre
Modified: 2016-10-01 12:26 UTC (History)
0 users

See Also:
Kernel Version: 4.5.5
Tree: Mainline
Regression: No


Attachments

Description Mathieu Malaterre 2016-06-07 13:48:28 UTC
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)
[...]
Comment 1 Mathieu Malaterre 2016-10-01 12:24:54 UTC
As additional comment, the naive approach of integrating the code from module radeon into radeonfb module did not work, as mentionned in:

https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-October/149375.html

Note You need to log in before you can comment on or make changes to this bug.