On 2016-01-21, Karsten Merker wrote: > On Thu, Jan 21, 2016 at 09:55:00PM +0100, Johannes Berg wrote: >> Machine: SolidRun HummingBoard Dual/Quad >> Kernel-Flavors: armmp >> DTB-Id: imx6q-hummingboard.dtb >> Boot-Script-Path: /boot/boot.scr >> U-Boot-Script-Name: bootscr.cubox-i >> Required-Packages: u-boot-tools >> >> One can use the Cubox-i instead, but then PCI-E won't work, and it'd >> be necessary to create /etc/flash-kernel/machine. > > Hello, > > the flash-kernel machine database in stretch and sid already contains an > entry for the SolidRun HummingBoard Dual/Quad: > > https://anonscm.debian.org/cgit/d-i/flash-kernel.git/commit/?id=e903f3d5d99b6795f59ab67be33dc79104e8096f > > The only difference to the one above is that is uses > > U-Boot-Script-Name: bootscr.uboot-generic > > instead of > > U-Boot-Script-Name: bootscr.cubox-i > > but according to Vagrant Cascadian (in CC) that should work. I have a hummingboard-i1, hummingboard-i2ex and cubox-i4pro that all worked with flash-kernel, kernel in debian, and u-boot in debian when I tested them all, and I continue to use them regularly. The generated bootscripts may not work correctly with u-boot that the vendor supplies, however. So you may need to update the u-boot version. live well, vagrant
Attachment:
signature.asc
Description: PGP signature