All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Hilliard <thirtythreeforty@gmail.com>
To: Paul Burton <paul.burton@mips.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	George Hilliard <thirtythreeforty@gmail.com>
Subject: [RESEND PATCH] mips: ralink: allow zboot
Date: Thu, 21 Mar 2019 11:03:34 -0600	[thread overview]
Message-ID: <20190321170334.15122-2-thirtythreeforty@gmail.com> (raw)
In-Reply-To: <20190321170334.15122-1-thirtythreeforty@gmail.com>

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 <thirtythreeforty@gmail.com>
---
 arch/mips/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 4a5f5b0ee9a9..b286fbbd9699 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -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


  reply	other threads:[~2019-03-21 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 17:03 [RESEND PATCH 0/1] mips: ralink: allow zboot George Hilliard
2019-03-21 17:03 ` George Hilliard [this message]
2019-03-21 22:01   ` [RESEND PATCH] " Aaro Koskinen
2019-03-21 23:10     ` George Hilliard
2019-03-21 23:40       ` Paul Burton
2019-03-22  0:29         ` George Hilliard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190321170334.15122-2-thirtythreeforty@gmail.com \
    --to=thirtythreeforty@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul.burton@mips.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.