public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: scott.branden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER
Date: Wed, 29 Aug 2018 11:59:36 -0700	[thread overview]
Message-ID: <fb07b89d-d427-5e59-9f17-b12df26284ec@broadcom.com> (raw)
In-Reply-To: <CAOesGMhjcJ1p3QcEYb9fsx3fMXAOsgR2njOq=VKgEbWGwJi36g@mail.gmail.com>

Hi Olof,


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

  reply	other threads:[~2018-08-29 18:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 17:21 [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER Scott Branden
2018-08-29 18:44 ` Olof Johansson
2018-08-29 18:59   ` Scott Branden [this message]
2018-08-30  5:54     ` Ard Biesheuvel
2018-08-30 15:06       ` Olof Johansson
2018-08-30 16:23         ` Ard Biesheuvel
2018-08-31 21:28           ` Scott Branden
2018-09-02  2:54           ` Olof Johansson
2018-09-04  6:23             ` Ard Biesheuvel
2018-09-04 10:13               ` Grant Likely
2018-09-04 17:19                 ` Scott Branden
2018-09-05  9:40                   ` Ard Biesheuvel
2018-09-05 17:27                     ` Scott Branden
2018-09-05 18:00                       ` Grant Likely
2018-09-05 18:04                         ` Scott Branden
2018-09-09 11:07                           ` Catalin Marinas
2018-09-09 15:55                             ` Ard Biesheuvel
2018-09-04 17:28                 ` Olof Johansson
2018-09-05  9:37                 ` Ard Biesheuvel
2018-09-05 19:09                   ` Grant Likely
2018-09-10 17:53                 ` Scott Branden
2018-09-10 18:01                   ` Olof Johansson
2018-09-10 18:08                     ` Ard Biesheuvel
2018-09-13 20:22                       ` Scott Branden
2018-09-14  6:06                         ` Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb07b89d-d427-5e59-9f17-b12df26284ec@broadcom.com \
    --to=scott.branden@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox