Hi! Martin Michlmayr <t...@cyrius.com> writes: > I was just looking at this bug report and it seems Karsten was never > copied on Christoph's last email (see below).
Sorry for that. And I just didn't want to nag if people are busy. Karsten Merker <mer...@debian.org> writes: > that looks good. With this environment, using the "generic" > boot script should work. > > Christoph, could you perform a test with a current u-boot by > applying my environment patch on top of u-boot v2016.11 and > putting the follwing stanza into /etc/flash-kernel/db ? > > Machine: SolidRun Clearfog A1 > Kernel-Flavors: armmp armmp-lpae > Boot-Script-Path: /boot/boot.scr > DTB-Id: armada-388-clearfog.dtb > U-Boot-Script-Name: bootscr.uboot-generic > Required-Packages: u-boot-tools > > (This stanza is based on the assumption that booting plain > initrds works when bootz is passed the corresponding filesize. I > still don't understand why you got a "Wrong Ramdisk Image Format" > when manually booting a plain initrd with u-boot v2016.09.) > > With the aforementioned stanza, running flash-kernel on the > commandline should generate a proper boot script in > /boot/boot.scr that should be automatically loaded by u-boot on > reboot. I'll try to get the results today/tomorrow night .. if I don't reply it'll be mid-january unfortunately Christoph
signature.asc
Description: PGP signature
