mips: ralink: allow zboot
PATCH 1/1 mips: ralink: allow zboot
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.
Tested on an MT7688 with U-Boot doing LZMA decompression of uImage.
--- arch/mips/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/mips/Kconfig +1 -0
@@ -619,6 +619,7 @@ config RALINK select SYS_SUPPORTS_32BIT_KERNEL select SYS_SUPPORTS_LITTLE_ENDIAN select SYS_SUPPORTS_MIPS16 + select SYS_SUPPORTS_ZBOOT select SYS_HAS_EARLY_PRINTK select CLKDEV_LOOKUP select ARCH_HAS_RESET_CONTROLLER
Signature · 1 line
2.21.0
Actually, I just thought about this: do I need to do a make olddefconfig for all the ralink-based defconfigs to let them choose a default compression method? (I'm somewhat new to kernel contributions, sorry if this is obvious.)
Thanks,
George
Quoted 29 lines · George Hilliard
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.
Tested on an MT7688 with U-Boot doing LZMA decompression of uImage.
Signed-off-by George Hilliard <[email protected]>--- arch/mips/Kconfig | 1 + 1 file changed, 1 insertion(+)arch/mips/Kconfig +1
-1@@ -619,6 +619,7 @@ config RALINK select SYS_SUPPORTS_32BIT_KERNEL select SYS_SUPPORTS_LITTLE_ENDIAN select SYS_SUPPORTS_MIPS16 + select SYS_SUPPORTS_ZBOOT select SYS_HAS_EARLY_PRINTK select CLKDEV_LOOKUP select ARCH_HAS_RESET_CONTROLLER --2.21.0