From: Christian Lamparter <chunkeey@gmail•com>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: Paul Mackerras <paulus@samba•org>,
Pawel Dembicki <paweldembicki@gmail•com>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: powerpc: Enable kernel XZ compression option on 44x
Date: Fri, 08 Feb 2019 16:17:56 +0100 [thread overview]
Message-ID: <2535516.UbJpQZMh7o@debian64> (raw)
In-Reply-To: <43wwMR1cjjz9sPG@ozlabs.org>
On Friday, February 8, 2019 2:02:41 PM CET Michael Ellerman wrote:
> On Thu, 2019-01-31 at 20:59:04 UTC, Christian Lamparter wrote:
> > Enable kernel XZ compression option on 44x.
> > Tested on a Western Digital - MyBook Live NAS.
> > It takes 22 seconds for the 800 MHz CPU to decompress
> > and boot a 2.63 MiB XZ-compressed kernel simpleImage.
> >
> > Signed-off-by: Christian Lamparter <chunkeey@gmail•com>
>
> Applied to powerpc next, thanks.
>
> https://git.kernel.org/powerpc/c/423bfc69d7f491c47fc35921f7d460be
>
> cheers
>
Hello,
I'm happy to report that a xz compressed kernel (as simpleImage)
also booted on a TP-Link WDR4900-v1 (Freescale P1014):
<https://github.com/openwrt/openwrt/pull/1773#issuecomment-461082045>
Hence, I'm inclined to also add PPC_85xx to list in /arch/powerpc/KConfig
|select HAVE_KERNEL_XZ if PPC_BOOK3S || 44x || PPC_85xx
But on the other hand, it could very well be that more or all? PPC
would benifit from having HAVE_KERNEL_XZ available. What do you think?
(If you know of any interesting ARCHs, I could ask around too.)
Regards,
Christian
prev parent reply other threads:[~2019-02-08 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 20:59 [PATCH] powerpc: Enable kernel XZ compression option on 44x Christian Lamparter
2019-02-08 13:02 ` Michael Ellerman
2019-02-08 15:17 ` Christian Lamparter [this message]
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=2535516.UbJpQZMh7o@debian64 \
--to=chunkeey@gmail$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
--cc=paweldembicki@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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