From: Will Deacon <will.deacon@arm.com>
To: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arch/arm64: Add the various compression methods to the default config
Date: Sat, 19 Jan 2019 21:02:23 +0000 [thread overview]
Message-ID: <20190119210221.GA30173@brain-police> (raw)
In-Reply-To: <20190119185540.20526-1-tobias.johannes.klausmann@mni.thm.de>
On Sat, Jan 19, 2019 at 07:55:40PM +0100, Tobias Klausmann wrote:
> There is no reason having arm64 not select these configurations by
> default!
>
> Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
> ---
> arch/arm64/Kconfig | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index a4168d366127..91a5e1cd7279 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -140,6 +140,11 @@ config ARM64
> select HAVE_GENERIC_DMA_COHERENT
> select HAVE_HW_BREAKPOINT if PERF_EVENTS
> select HAVE_IRQ_TIME_ACCOUNTING
> + select HAVE_KERNEL_GZIP
> + select HAVE_KERNEL_LZ4
> + select HAVE_KERNEL_LZMA
> + select HAVE_KERNEL_LZO
> + select HAVE_KERNEL_XZ
> select HAVE_MEMBLOCK_NODE_MAP if NUMA
> select HAVE_NMI
> select HAVE_PATA_PLATFORM
I don't really understand what this patch achieves. We don't have a built-in
decompressor for arm64, as we defer to the bootloader to handle that for us
instead. The Image.gz target already produces a gzipped kernel payload.
What are you trying to do?
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-19 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 18:55 [PATCH] arch/arm64: Add the various compression methods to the default config Tobias Klausmann
2019-01-19 21:02 ` Will Deacon [this message]
2019-01-21 0:38 ` Tobias Klausmann
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=20190119210221.GA30173@brain-police \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=tobias.johannes.klausmann@mni.thm.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox