On 2019-05-12, Karsten Merker wrote: > On Sun, May 12, 2019 at 10:40:39AM +0200, Domenico Andreoli wrote: >> +Machine: FriendlyARM NanoPi NEO 2 >> +Kernel-Flavors: arm64 >> +Boot-Script-Path: /boot/boot.scr >> +DTB-Id: allwinner/sun50i-h5-nanopi-neo2.dtb >> +U-Boot-Script-Name: bootscr.uboot-generic >> +Required-Packages: u-boot-tools >> + >> >> I was not able to cross-build the arm64 installer from amd64 so the >> patch is not tested. >> >> Please mind that the NanoPi NEO 2 target for u-boot has just been merged >> in sid so it's not yet in Buster. ... > while the change looks ok to me, I'd very much prefer if it was > actually tested before committing it (the same is true for > bug#928863).
Would it be ok to test it in-place on an installed system by adding the entry to /etc/flash-kernel/db? That's how I usually test boards I've added. Or do you not have an installed system? It's a bit difficult to fully test within debian-installer, as the installer typically pulls in .udebs from the archive, and you have a bit of chicken-and-egg problem to require testing from d-i, or a lot of manual fiddling within the installer. You could also patch /target/etc/flash-kernel/db or /target/usr/share/flash-kernel/db from within the install at just the right moment ... live well, vagrant
signature.asc
Description: PGP signature
