[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMhjcJ1p3QcEYb9fsx3fMXAOsgR2njOq=VKgEbWGwJi36g@mail.gmail.com>
Date: Wed, 29 Aug 2018 11:44:58 -0700
From: Olof Johansson <olof@...om.net>
To: Scott Branden <scott.branden@...adcom.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Arnd Bergmann <arnd@...db.de>,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER
Hi,
On Wed, Aug 29, 2018 at 10:21 AM, Scott Branden
<scott.branden@...adcom.com> wrote:
> Enable EFI_ARMSTUB_DTB_LOADER to add support for the dtb= command line
> parameter to function with efi loader.
>
> Required to boot on existing bootloaders that do not support devicetree
> provided by the platform or by the bootloader.
>
> Fixes: 3d7ee348aa41 ("efi/libstub/arm: Add opt-in Kconfig option for the DTB loader")
> Signed-off-by: Scott Branden <scott.branden@...adcom.com>
Why did Ard create an option for this if it's just going be turned on
in default configs? Doesn't make sense to me.
It would help to know what firmware still is crippled and how common
it is, since it's been a few years that this has been a requirement by
now.
-Olof
Powered by blists - more mailing lists