2016-02-24 19:06 GMT+01:00 Lubomir Rintel <lkundrak(a)v3.sk>:
> On Mon, 2016-02-15 at 20:34 +0100, Jérôme Fenal wrote:
>> 2016-02-15 16:59 GMT+01:00 Lubomir Rintel <lkundrak(a)v3.sk>:
>> > On Mon, 2016-02-15 at 15:18 +0100, Jérôme Fenal wrote:
>> > > 2016-02-15 13:02 GMT+01:00 Peter Robinson
<pbrobinson(a)gmail.com>:
>> > > > Hi Lubomir,
>> > >
>> > > Hi all,
>> > >
>> > > > > 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
>> > >
>> > > What do we miss, besides this BZ, to get Fedora running on the
>> > > Rappberry Pi 2?
>> >
>> > u-boot fixes are needed to build/run the board. All likely
>> > to be included in 2016/03 upstream:
>> >
>> > *
http://lists.denx.de/pipermail/u-boot/2016-February/245385.html
>> > To fix the uboot-tools build
>> >
>> > * 89ca1000 ARM: rpi: set fdt_high in the default environment
>> > This, to load fdt where VMSPLIT_3G kernel can reach it.
>> >
>> > *
http://lists.denx.de/pipermail/u-boot/2016-February/245402.html
>> > Alike, for the ramdisk.
>> >
>> > That is the bare minimim to get the system to boot.
>> > There's a couple of known flaws and likely some unknown:
>> >
>> > * Some drivers are missing:
http://elinux.org/RPi_Upstreaming
>> >
>> > * The ethernet MAC address is random. Fix headed for 4.6.
>> >
>> > * VC4 is not bound to the device tree. And the configfs interface
>> > to
>> > the overlays is not yet here. This could possibly be worked around
>> > by
>> > an userspace tool that would generate a desired dtb from fragments.
>> >
>> > * Not sure if simplefb works. It certainly does not for my DSI
>> > display.
>> > Didn't try with newer firmware or HDMI, will look into that.
>> >
>> > > With also Eric Anholt's new VC4 driver[1], that should get us
>> > > closer
>> > > and closer from a fully-supportable Pi 2.
>> > >
>> > > If needed, I just received a bunch of Pi 2 (5 of them), that I'll
>> > > be
>> > > happy to use to test, either within Red Hat premises, or from my
>> > > personal internet connection.
>> >
>> > I'll try to share an image you could run tomorrow.
>>
>> Thank you, I'll try it later this week-end, my week is almost full.
>
> Here's what I have now. Mostly stock Fedora + kernel configuration and
> patches to make ethernet mac address stable (would work without them
> too):
>
>
https://pignus.computer/pub/experimental/armv7hl/
>
Excellent!
I'm giving it a try in a few minutes! :)
Not booting.
The green LED is steadily on, not flashing, so it does not even boot.
I also added files from the firmware rpi githup repo, did not help:
# insert SD card in my F23 laptop
cd /run/media/jfenal/__boot/
cp /home/jfenal/dev/firmware/boot/{bcm270*,bootcode.bin,fixup*,start*} .
mkdir overlays
rsync -av /home/jfenal/dev/firmware/boot/overlays/ overlays/
Didn't work either.
I've ordered a serial console cable, it will arrive when it will arrive...
If you have any ideas... ?
--
Jérôme Fenal