[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240504193446.196886-1-emil.renner.berthing@canonical.com>
Date: Sat, 4 May 2024 21:34:37 +0200
From: Emil Renner Berthing <emil.renner.berthing@...onical.com>
To: linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org,
linux-kbuild@...r.kernel.org
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nicolas Schier <nicolas@...sle.eu>,
Nick Terrell <terrelln@...com>
Subject: [PATCH v2 0/2] riscv: make image compression configurable
Masahiro's patch[1] made me wonder why we're not just using KBUILD_IMAGE
to determine which (possibly compressed) kernel image to use in 'make
tar-pkg' like other architectures do. It turns out we're always setting
KBUILD_IMAGE to the uncompressed Image file and then compressing it into
the Image.gz file afterwards.
This series fixes that so the compression method is configurable and
KBUILD_IMAGE is set to the chosen (possibly uncompressed) kernel image
which is then used by targets like 'make install' and 'make bindeb-pkg' and
'make tar-pkg'.
Changes in v2:
- Rebase on riscv/for-next
- Use boot-image-$(CONFIG_..) := assignments rather than ifeq train in
patch 1
- Drop patch 3 already applied to kbuild/for-next
Emil Renner Berthing (2):
riscv: make image compression configurable
riscv: show help string for riscv-specific targets
arch/riscv/Kconfig | 7 +++++
arch/riscv/Makefile | 55 ++++++++++++++++++++++++--------------
arch/riscv/boot/install.sh | 9 ++++---
3 files changed, 48 insertions(+), 23 deletions(-)
--
2.43.0
Powered by blists - more mailing lists