lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2440a64-f40d-7923-1c7b-1430ab557e59@linaro.org>
Date:   Fri, 19 Aug 2022 10:45:38 +0300
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Arnd Bergmann <arnd@...nel.org>,
        linux-arm-kernel@...ts.infradead.org
Cc:     linux-kernel@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
        Russell King <linux@...linux.org.uk>,
        Linus Walleij <linus.walleij@...aro.org>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Ard Biesheuvel <ardb@...nel.org>, Sekhar Nori <nsekhar@...com>,
        Bartosz Golaszewski <brgl@...ev.pl>,
        Shawn Guo <shawnguo@...nel.org>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Andrew Lunn <andrew@...n.ch>,
        Gregory Clement <gregory.clement@...tlin.com>,
        Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH 1/5] ARM: remove obsolete Makefile.boot infrastructure

On 18/08/2022 17:56, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
> 
> There are a number of old Makefile.boot files that remain from the
> multiplatform conversion, and three that are still in use.
> 
> These provide the "ZRELADDR", "PARAMS_PHYS" and "INITRD_PHYS" values
> that are platform specific. It turns out that we can generally just
> derive this from information that is available elsewhere:
> 
> - ZRELADDR is normally detected at runtime with the
>   CONFIG_AUTO_ZRELADDR flag, but also needed to be passed to
>   for 'make uImage'. In a multiplatform kernel, one always has
>   to pass this as the $(LOADADDR) variable, but in the StrongARM
>   kernels we can derive it from the sum of $(CONFIG_PHYS_OFFSET)
>   and $(TEXT_OFFSET) that are already known.
> 
> - PARAMS_PHYS and INITRD_PHYS are only used for bootpImage, which
>   in turn is only used for the pre-ATAGS 'param_struct' based boot
>   interface on StrongARM based machines with old boot loaders.
>   They can both be derived from CONFIG_PHYS_OFFSET and a machine
>   specific offset for the initrd, so all of the logic for these
>   can be part of arch/arm/boot/bootp/Makefile.
> 
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
>  arch/arm/Kconfig                       |  2 +-
>  arch/arm/Makefile                      |  4 +--
>  arch/arm/boot/Makefile                 | 27 ++++++--------------
>  arch/arm/boot/bootp/Makefile           | 35 ++++++++++++++++++++++++--
>  arch/arm/mach-at91/Makefile.boot       |  4 ---
>  arch/arm/mach-davinci/Makefile.boot    |  8 ------
>  arch/arm/mach-dove/Makefile.boot       |  4 ---
>  arch/arm/mach-ep93xx/Makefile.boot     |  2 --
>  arch/arm/mach-footbridge/Makefile.boot |  5 ----
>  arch/arm/mach-imx/Makefile.boot        |  0
>  arch/arm/mach-iop32x/Makefile.boot     |  4 ---
>  arch/arm/mach-lpc18xx/Makefile.boot    |  4 ---
>  arch/arm/mach-lpc32xx/Makefile.boot    |  4 ---
>  arch/arm/mach-omap1/Makefile.boot      |  4 ---
>  arch/arm/mach-rpc/Makefile.boot        |  5 ----
>  arch/arm/mach-s3c/Makefile.boot        |  9 -------


Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> # s3c

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ