On Wed, 01 Feb 2017 13:35:40 -0800 Vagrant Cascadian <vagrant@debian.org> wrote: >So, when building an arm64 linux package using Debian's packaging, it >builds a package where /boot/vmlinuz-VERSION is uncompressed, and >bootloaders such as u-boot can boot it with booti. > >But when building a mainline kernel with "make bindeb-pkg" it produces >a package where /boot/vmlinuz-VERSION is compressed with gzip, and >u-boot's booti fails to boot it. Simply uncompressing the >/boot/vmlinuz-VERSION then allows u-boot's booti command to work >properly. > >I seem to recall a similar issue with grub not booting the compressed >image, but it's been a while since I've tried. > > >Debian's linux packaging seems to manually specify the image type in >debian/config/arm64/defines: > > image-file: arch/arm64/boot/Image > >Upstream defaults to Image.gz in arch/arm64/Makefile: > > KBUILD_IMAGE := Image.gz > > >Are there platforms on arm64 that use Image.gz? > >Should upstream default to "Image" instead, or should upstream's >bindeb-pkg target default arm64 builds to use KBUILD_IMAGE=Image, to be >consistant with Debian's linux packages? > > >live well, > vagrant I *believe* that the name vmlinuz implies compression, whereas the name vmlinux does not. could it simply be misnamed? -C
Attachment:
pgpY3rjqH6KGg.pgp
Description: OpenPGP digital signature