Because we are using image type "kernel_noload" instead of "kernel" for
GENERIC. The header on "kernel" type images contains a load address, and
U-Boot will uncompress the kernel there. For "kernel_noload" type images
there is no load address specified, with the expectation that the kernel
will be executed in place.
It's probably not very hard to fix U-Boot to handle this case..
On Thu, 14 Mar 2019, Manuel Bouyer wrote:
On Thu, Mar 14, 2019 at 10:22:43AM +0000, Jared D. McNeill wrote:
Module Name: src
Committed By: jmcneill
Date: Thu Mar 14 10:22:43 UTC 2019
Modified Files:
src/sys/arch/evbarm/conf: mk.generic
Log Message:
U-Boot fails to boot a compressed kernel_noload image, so stop emitting
them.
Any idea why it doesn't work any more ?
--
Manuel Bouyer <bou...@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
