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  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]
Date:   Wed, 29 Aug 2018 11:59:36 -0700
From:   Scott Branden <>
To:     Olof Johansson <>,
        Ard Biesheuvel <>
Cc:     Catalin Marinas <>,
        Will Deacon <>,
        Arnd Bergmann <>,
        BCM Kernel Feedback <>,
        Linux ARM Mailing List <>,
        Linux Kernel Mailing List <>
Subject: Re: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER

Hi Olof,

On 18-08-29 11:44 AM, Olof Johansson wrote:
> Hi,
> On Wed, Aug 29, 2018 at 10:21 AM, Scott Branden
> <> 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 <>
> 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.
Broadcom NS2 and Stingray in current development and production need 
this option in the kernel enabled in order to boot.
> -Olof

Powered by blists - more mailing lists