arm64: Image vs. Image.gz

2017-02-01 Thread Vagrant Cascadian
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

Re: arm64: Image vs. Image.gz

2017-02-01 Thread Christopher Barry
On Wed, 01 Feb 2017 13:35:40 -0800 Vagrant Cascadian 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 "ma

Re: arm64: Image vs. Image.gz

2017-02-03 Thread Riku Voipio
On Wed, Feb 01, 2017 at 01:35:40PM -0800, Vagrant Cascadian 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

Re: arm64: Image vs. Image.gz

2017-02-03 Thread dann frazier
On Fri, Feb 03, 2017 at 12:00:54PM +, Riku Voipio wrote: > On Wed, Feb 01, 2017 at 01:35:40PM -0800, Vagrant Cascadian 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