Hi Lubomir, > Seems like there's not much that's left to be done for stock Fedora to > boot on Raspberry Pi 2 successfully [1]. There's not much, I've > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1308355 > > One bit that notably prevents us from spinning an image that would boot > on RPi2 board solely from the Fedora packages is the VC4 firmware. Yes, it's one, there's a bunch of others, the kernel now should be mostly upstream, it's on my list (it's very long) to enable this and test it. We also need to be able to use u-boot so that we can do standard kernel upgrades/rollbacks as well as deal with the fact the firmware needs a VFAT partition without having to have the confusion and QA of twice the amount of images produced > It seems to have a license [2] that's not compatible with Fedora's > "Redistributable, no modification permitted" license for binary > firmware blobs: it seems to have a usage restriction: We spoke with the RPi foundation about this years ago to get some adjustments made for distro distribution, and then Legal and got the appropriate exceptions, then the board (as it was then) to get the approval there. Basically the work has been done already and firmware has been packaged in Fedora since last June [1]. [1] http://pkgs.fedoraproject.org/cgit/rpms/bcm283x-firmware.git >> * This software may only be used for the purposes of developing for, >> running or using a Raspberry Pi device. > > [2] https://github.com/raspberrypi/firmware/blob/master/boot/LICENCE.broadcom > > The way to go now seems to be to spin a remix with the firmware added. > > Does it make sense to talk to Broadcom or Raspberry Pi Foundation/Ltd > and asking them to lift the restriction? I doubt it would cause any > practical difference to them. Does anyone have a contact at Broadcom or > Raspberry Pi I could talk to? We had those conversations well over 2 years ago long before the v2 was announced. Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/arm@xxxxxxxxxxxxxxxxxxxxxxx