From: "Christian König" <deathsimple@vodafone.de>
To: Mathieu Malaterre <malat@debian.org>,
Alex Deucher <alexdeucher@gmail.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref]
Date: Tue, 7 Jun 2016 14:28:38 +0200 [thread overview]
Message-ID: <5756BDF6.4070301@vodafone.de> (raw)
In-Reply-To: <CA+7wUsw36w=LUzG5-v56Qy444+Ze2Fyf98HH8COkWmR7F9=7Yg@mail.gmail.com>
Am 07.06.2016 um 14:19 schrieb Mathieu Malaterre:
> On Tue, Jun 7, 2016 at 8:05 AM, Mathieu Malaterre <malat@debian.org> wrote:
>> Hi Alex,
>>
>> On Mon, Jun 6, 2016 at 7:20 PM, Alex Deucher <alexdeucher@gmail.com> wrote:
>>> On Mon, Jun 6, 2016 at 1:16 PM, Marek Olšák <maraeo@gmail.com> wrote:
>>>> [+ dri-devel]
>>>>
>>>> On Mon, Jun 6, 2016 at 8:42 AM, Mathieu Malaterre <malat@debian.org> wrote:
>>>>> Hi,
>>>>>
>>>>> Before reporting a possible invalid bug report. Does anyone knows why
>>>>> radeaonfb is not configured the same way radeon is ? For instance on a
>>>>> PowerPC machine, when Open Firmware Frame Buffer is used (OFfb), I
>>>>> cannot `modprobe radeonfb` (but I can load `radeon`). It 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
>>>>>
>>>>> Is the above correct ?
>>> Yes, probably. But is there any reason why you'd want to use radeonfb
>>> rather than radeon?
>> I'll check with the debian-installer team if this is possible. Right
>> now the debian-installer is setup to use `radeonfb` (at least on
>> PowerPC) during the text-based installation.
>>
>> ref: https://bugs.debian.org/825840#77
> [between a rock and a hard place]
>
> So it seems there would be a risk moving from radeonfb to radeon, esp.
> since Debian does not distribute (at least by default) the firmware
> during installation: https://bugs.debian.org/826629#12.
>
> I'll report the bug against radeonfb and see if I can provide a patch.
radeon should be able to offer the same functionality as radeonfb even
without firmware.
But saying so that functionality is usually rarely tested.
Regards,
Christian.
>
> -M
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
prev parent reply other threads:[~2016-06-07 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+7wUsxEuNV-Pd0+ZNOvrgORUH7iXyFjRZyAMf-Visq9qUWPew@mail.gmail.com>
2016-06-06 17:16 ` radeonfb: BAR 0: can't reserve [mem 0x98000000-0x9fffffff pref] Marek Olšák
2016-06-06 17:20 ` [Mesa-dev] " Alex Deucher
2016-06-07 6:05 ` Mathieu Malaterre
2016-06-07 12:19 ` [Mesa-dev] " Mathieu Malaterre
2016-06-07 12:28 ` Christian König [this message]
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=5756BDF6.4070301@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=malat@debian.org \
--cc=mesa-dev@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