Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp771444ybi; Fri, 14 Jun 2019 03:07:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqxdwgwjSv/zOi2Js3zrFtsAIujJvEf+JLgKZDmZgyGgvKlAz5zpx6toYz3vD7It/KXVZZ0s X-Received: by 2002:aa7:83d4:: with SMTP id j20mr100717858pfn.90.1560506842722; Fri, 14 Jun 2019 03:07:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560506842; cv=none; d=google.com; s=arc-20160816; b=dG+ET7jZqonbAWXv5xM1z3seL5IqaSXnafbWGa/b51VsDDsEohAe99808JJd7bWFr/ eZu25+uH18xIC6uPcHH16G00DjaaJhAuiLck584UbPVay3v0RynzLigML2vRUgcHmq7h nfyDYv8AOBPEBMiRUZWMWIZVZar0VmyXBvJHDvwvDpOAt4wCSOyh0Iaoq4p786r6b+eT upy8Ko6g0AYmd6knuEQDSNrvCFdt5EwgL5n4GUjOhV961BTHmrPHe5S2om3KiR3Jtg+a xFb8V5olUodaJoCO5bAL4jdKWhcsrtGUcSatOvK4LgQDjUueSuYeNVyANklth/QHdnF9 k8RQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=H6U3dIX2SVKCwZUsFTw72sro38m1Gqkl8Z8i5rZXXBk=; b=eGOb/glbYr2mJ7+ftYfOsJ+TlUErGmIcC253d9QnEesu5kgdu42YQ88DKGej4wFBEs BpFXFgFe6tA+qDnmq/xppavnnCbsc9+Nq4Mb5O0/QKWAgFYU0YkkERIp0bhcQjbZBbEk Q5H9rqPl/XHY19YXm1m+321joV1TMvCukWrGz1b7m5vnobpJHmO0h/i4rk2t52XaxicZ CVSD/NxWgpSzew1ATTmTXHfSk+sWHzH3yEA64Ls9qbY4z0TfKlXr+AZuLzkcFNVIW5HU i3sZNUZ7TqZi4SUWXqTVei0wkegpJxf50oORulLRz0wlV148sbyHVtaBonaxIwRdGLxn yUjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=aMGMnR3v; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s187si1953781pfb.255.2019.06.14.03.07.05; Fri, 14 Jun 2019 03:07:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=aMGMnR3v; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727116AbfFNKGw (ORCPT + 99 others); Fri, 14 Jun 2019 06:06:52 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:59532 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726370AbfFNKGw (ORCPT ); Fri, 14 Jun 2019 06:06:52 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 45QGVJ0nt7z9vDbm; Fri, 14 Jun 2019 12:06:48 +0200 (CEST) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=aMGMnR3v; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id X4TVEgvEUXXh; Fri, 14 Jun 2019 12:06:48 +0200 (CEST) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 45QGVH6rw3z9vDbk; Fri, 14 Jun 2019 12:06:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1560506807; bh=H6U3dIX2SVKCwZUsFTw72sro38m1Gqkl8Z8i5rZXXBk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=aMGMnR3vGNtc96FQA7Tlx/Xb6c2k5dcWmki0WikZ3pCbwAQ5boG68yvaraxbba0gA SmDmrwVTNjTIsBuCKtj2ADsZ/+uqrgL5K6rjuv6tuoLuYZylcEBbgrPXVO+yGDPymj LRH1EF2eY01DWKSxkoYMNtpIqFxfEAG5lIhoLS7A= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 27A3F8B7AD; Fri, 14 Jun 2019 12:06:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 8qQm5fcEnkLQ; Fri, 14 Jun 2019 12:06:49 +0200 (CEST) Received: from PO15451 (po15451.idsi0.si.c-s.fr [172.25.230.107]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 02E4A8B7AC; Fri, 14 Jun 2019 12:06:49 +0200 (CEST) Subject: Re: [PATCH] powerpc: Enable kernel XZ compression option on PPC_85xx To: Michael Ellerman , Daniel Axtens , Pawel Dembicki Cc: Christian Lamparter , linux-kernel@vger.kernel.org, Paul Mackerras , linuxppc-dev@lists.ozlabs.org References: <20190603164115.27471-1-paweldembicki@gmail.com> <877e9qp3ou.fsf@dja-thinkpad.axtens.net> <87ftodempa.fsf@concordia.ellerman.id.au> From: Christophe Leroy Message-ID: Date: Fri, 14 Jun 2019 12:06:48 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <87ftodempa.fsf@concordia.ellerman.id.au> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 13/06/2019 à 13:42, Michael Ellerman a écrit : > Daniel Axtens writes: >> Pawel Dembicki writes: >> >>> Enable kernel XZ compression option on PPC_85xx. Tested with >>> simpleImage on TP-Link TL-WDR4900 (Freescale P1014 processor). >>> >>> Suggested-by: Christian Lamparter >>> Signed-off-by: Pawel Dembicki >>> --- >>> arch/powerpc/Kconfig | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig >>> index 8c1c636308c8..daf4cb968922 100644 >>> --- a/arch/powerpc/Kconfig >>> +++ b/arch/powerpc/Kconfig >>> @@ -196,7 +196,7 @@ config PPC >>> select HAVE_IOREMAP_PROT >>> select HAVE_IRQ_EXIT_ON_IRQ_STACK >>> select HAVE_KERNEL_GZIP >>> - select HAVE_KERNEL_XZ if PPC_BOOK3S || 44x >>> + select HAVE_KERNEL_XZ if PPC_BOOK3S || 44x || PPC_85xx >> >> (I'm not super well versed in the compression stuff, so apologies if >> this is a dumb question.) If it's this simple, is there any reason we >> can't turn it on generally, or convert it to a blacklist of platforms >> known not to work? > > For some platforms enabling XZ requires that your u-boot has XZ support, > and I'm not very clear on when that support landed in u-boot and what > boards have it. And there are boards out there with old/custom u-boots > that effectively can't be updated. I don't think that it has anything to do with u-boot. AFAIK, today's mainline U-boot only supports GZIP (by default) and the following optional ones: LZO, LZMA, LZ4. If we want to set additional compression types for u-boot, it is not enough to select HAVE_KERNEL_XXXX, we also have to update uImage generation scripts. See the series I sent some time ago: https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=104153 I'll resent it without bzip2 as today's uboot doesn't support bzip2 anymore. > > But as a server guy I don't really know the details of all that very > well. So if someone tells me that we should enable XZ for everything, or > as you say just black list some platforms, then that's fine by me. > I guess we first need to understand how this is used. Christophe