The firmware should be acceptable for immediate packaging in Fedora:
https://fedoraproject.org/wiki/Packaging:LicensingGuidelines?rd=Packaging/LicensingGuidelines#Binary_Firmware

(I believe that page was amended explicitly to allow for the raspberry pi bootloader. It even mentions raspberry pi by name in the example.)

The firmware is still required to boot, because it still provides runtime services to userspace. Eventually it may go away, but probably not in 2015. I think you would chain to u-boot if you wanted u-boot in the mix.

Firmware upstream: https://github.com/raspberrypi/firmware

This video contains some info about the overall open source roadmap:
https://www.youtube.com/watch?v=EXDeketJNdk

Ultimately it is on people's radar but far off. (But could be accelerated by motivated individuals.)



Adam


On Wed, Feb 4, 2015 at 10:43 AM, Peter Robinson <pbrobinson@gmail.com> wrote:
Hi All,

As a follow up of the discussion that happened at the last ARM meeting
(and because 3 days post announcement of it I'm sick of repeating
myseld:-P ) I thought I'd outline the process for getting support for
the Raspberry Pi 2 into Fedora

The first phase I believe should be a remix, with the modified
packages required to support the install for that remix being is a
published repository, while we're awaiting all the bits to land
upstream.

The short term repository should only contain the following:
* kernel
* bootloader
* firmware
* mainline userspace packages that need non upstream pacakges

Everything else (eg xorg drivers) should be packaged up and go through
the standard package review process and be in mainline Fedora.

>From there we can spin a remix image for testing.

BUT before we get to that we need to review all the
projects/sources/packages that are needed and document what packages
are needed and where the upstream is located. In the case of firmware
we also need to ensure it's re-distributable. Does the GPU firmware
still boot or is it now possible to use the upstream u-boot support to
boot the device and then load the firmware via the kernel like other
standard drivers that need firmware, or do we even need binary
firmware any more?

I believe Seneca has volunteered to spear head this so it would be
great if they can start by documenting the above and post the details
of it in response to this mail so we can work out what needs to be
done and where in preparation for the remix, this will then give us a
good picture as well when we might be able to just support it by the
standard mainline process.

Regards,
Peter
_______________________________________________
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm