[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACmrr9hj6A_ZgbgO=bHuueav1FEc4jQ2-T9ddASa61Qe4mKR9g@mail.gmail.com>
Date: Thu, 21 Mar 2019 17:10:38 -0600
From: George Hilliard <thirtythreeforty@...il.com>
To: Aaro Koskinen <aaro.koskinen@....fi>
Cc: Paul Burton <paul.burton@...s.com>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] mips: ralink: allow zboot
My version of U-Boot complains if I compile out LZMA support:
---
=> tftpboot 0x81000000 uImage; tftpboot 0x84000000 hawkeye.dtb; bootm
0x81000000 - 0x84000000
(snip)
Bytes transferred = 7349 (1cb5 hex)
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-5.1.0-rc1
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1465871 Bytes = 1.4 MiB
Load Address: 80000000
Entry Point: 80344338
Verifying Checksum ... OK
## Flattened Device Tree blob at 84000000
Booting using the fdt blob at 0x84000000
Uncompressing Kernel Image ... Unimplemented compression type 3
exit not allowed from main input shell.
=>
---
Thanks,
George
On Thu, Mar 21, 2019 at 4:56 PM Aaro Koskinen <aaro.koskinen@....fi> wrote:
>
> Hi,
>
> On Thu, Mar 21, 2019 at 11:03:34AM -0600, George Hilliard wrote:
> > Architecturally, there's nothing preventing compressed images from
> > working. Bootloaders built with support for the various compression
> > methods can decompress and run the kernel. In practice, many
> > bootloaders do not support compressed images, but kernels for those
> > boards should just not be compressed.
>
> With zboot the decompressor is included in the image so no bootloader
> support is needed.
>
> A.
Powered by blists - more mailing lists