On Sun, 19 Nov 2023 07:43:30 -0700, Simon Glass wrote: > This little series corrects a problem I noticed with arm64 images, > where the kernel is not recognised if compression is used: > > U-Boot> tftp image.fit > Using ethernet@7d580000 device > TFTP from server 192.168.4.7; our IP address is 192.168.4.147 > Filename 'image.fit'. > Load address: 0x1000000 > Loading: ################################################## 23 MiB > 20.5 MiB/s > done > Bytes transferred = 24118272 (1700400 hex) > U-Boot> bootm > ## Loading kernel from FIT Image at 01000000 ... > Using 'conf-768' configuration > Trying 'kernel' kernel subimage > Description: Linux > Type: Kernel Image (no loading done) > Compression: gzip compressed > Data Start: 0x01000120 > Data Size: 13662338 Bytes = 13 MiB > Verifying Hash Integrity ... OK > Bad Linux ARM64 Image magic! > > [...]
Applied to u-boot/next, thanks! -- Tom