[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220307122142.GE14422@alpha.franken.de>
Date: Mon, 7 Mar 2022 13:21:42 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Paul Cercueil <paul@...pouillou.net>
Cc: YunQiang Su <yunqiang.su@...united.com>,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
od@...ndingux.net, stable@...r.kernel.org
Subject: Re: [PATCH] mips: Always permit to build u-boot images
On Sun, Mar 06, 2022 at 03:16:48PM +0000, Paul Cercueil wrote:
> The platforms where the kernel should be loaded above 0x8000.0000 do not
> support loading u-boot images, that doesn't mean that we shouldn't be
> able to generate them.
>
> Additionally, since commit 79876cc1d7b8 ("MIPS: new Kconfig option
> ZBOOT_LOAD_ADDRESS"), the $(zload-y) variable was no longer hardcoded,
> which made it impossible to use the uzImage.bin target.
>
> Fixes: 79876cc1d7b8 ("MIPS: new Kconfig option ZBOOT_LOAD_ADDRESS")
> Cc: <stable@...r.kernel.org>
> Signed-off-by: Paul Cercueil <paul@...pouillou.net>
> ---
> arch/mips/Makefile | 4 ----
> 1 file changed, 4 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists