Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp53812imm; Thu, 30 Aug 2018 08:09:06 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZ0I+4cOpRJEYfLT6k/YupVF/UuDDAZpQGGpzZVAA1l3Mprb0alTjWqOZuBMC9rA/+v6I3P X-Received: by 2002:a63:5a13:: with SMTP id o19-v6mr9997388pgb.75.1535641746325; Thu, 30 Aug 2018 08:09:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535641746; cv=none; d=google.com; s=arc-20160816; b=Q4stx0NO3Yh5DptY8VZaYrx0ogxtjhnJpJi8+pasb/qklStxHrbrIfyM8x3erzl4nM Q+RZ8mNiC4VGKdkdrPlGQog0/ZJ2B0ZL3dFg+IqXBZc1jabM8i9E/fv831BkjlfFQ1RO upMX3tOHvFHMLlPUgRAs561ix04ySojnf4xYKGx/+C+Ltgo0gMczoELz2XQ+qzgMkPzb TpLyHT0D7Q80eRCsbs3ykniOvu4P1OeoLWuDeWXDZsycH3PoAKSjZLzuoXCEMs/r5dh9 pmfA2hYjSjpAE2SdA7ywt4K8GhNZRUBG3PyLd90tCJOiOYZLrK6UxJ8BauZMDJABpdPz 2gCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=d+hduf7GdEs60i9JT8GVwOLw8yq7Cp1WN3KIRa/3IX0=; b=N11IMOiXkO0KXPa07GrB1la/EqxD+voYT5w4N9NEV5hyM0DIqWwXjn2K3l0j47rm2s QJQLRCBFrgy3T5N5r49FXdOiL9zNGlTkTykvULepXDal5d4CzYkRX573jYZZ9wVDmepJ Wm/08Txu2ENqVMWOBqz95Xnjisa9cqD2/ADLZ099fiUatYPx7jrcZRLAZLjeh8x5RqoG gkmvlcZUPWSEN7Hc1JBslwBhJfBQW1/VwNEzpbsiQC5CInhuv/aZ3nmBkH7GHbRCwhAF ZmdMS88ufBcTiPzu7IBFtYJAlQ43Z/O1j97l0mNW/1l7cxFkQ0wRfZKBEv5SPqxfVwus z1hg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lixom-net.20150623.gappssmtp.com header.s=20150623 header.b=IIUVGeF8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y1-v6si6823408pgf.146.2018.08.30.08.08.50; Thu, 30 Aug 2018 08:09:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@lixom-net.20150623.gappssmtp.com header.s=20150623 header.b=IIUVGeF8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728095AbeH3TJQ (ORCPT + 99 others); Thu, 30 Aug 2018 15:09:16 -0400 Received: from mail-lj1-f194.google.com ([209.85.208.194]:37192 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727388AbeH3TJP (ORCPT ); Thu, 30 Aug 2018 15:09:15 -0400 Received: by mail-lj1-f194.google.com with SMTP id v9-v6so7562804ljk.4 for ; Thu, 30 Aug 2018 08:06:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d+hduf7GdEs60i9JT8GVwOLw8yq7Cp1WN3KIRa/3IX0=; b=IIUVGeF8/7y4GtO0KV6vZiAULnZldYXpvzfIIoBFnpuDXzLEWsbwaDBFWn7mOaSFhY b1xCtmzuXssxuYJngRv7BO/9e8xIPRvMeY03OYu0PkwVBhMSHuuhS+uCoNSs06nqiRdT KxIWQgnAXZHP9LtfdtCLDcwjdjvHvxT6fD11sacwm2DQiUp4DWwO98K35XII4OHFoUno qh1B3uYZl1qU2vnuo2lRLILDHvvbnyNtJpm8AzTkp6sC6lr/WOIsY7dMxMaYN+Q9Kpwm 2mI21ZefZbCV0tO6nCvOKOnc1p1lx0QSP5tq0HcSLUbPVflR4T3i1zRouWyg/HXbScRl 9PKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d+hduf7GdEs60i9JT8GVwOLw8yq7Cp1WN3KIRa/3IX0=; b=jXZtAf4fVzVFhVochjCZCgkE87SmYoLzUjf/iQUOwdHcplBQQmITm89DhXUtqJO2jk kpVPqTBgFdMJh/IeyMXB/oEMT8bVCBWm+XfTWeiMTiy5C4y5zSUuNzzspy7M456XDWsi z+Y982lWlDUdsGe24zaCDHMb1+8Zcnpg4XAbhWbNVePh+1YhVrxprgEJMpnkMoPNii+7 WYVDHpRr6+u62W+1/XqwB2XTYTNKYA/B61bC1S0h2ydFI84qWYB6v6ZH1Y4DUdO2+8jI vi6O3X6NRatY/cVN8FdWOfuIm6Q7sWE+jAUp7Ikm5T8d4Shxt8wYELp5vjp1/XqwHx8Q A+fQ== X-Gm-Message-State: APzg51BjYxs3I+/UfXBMhLj6kUVBGwoNvUpuqq9Q0uMeKEwI/NoQRCBU EWE+bGpoQwQ4Pbvs1WHTsOZ19o+RzdGP40/JuAy2Ng== X-Received: by 2002:a2e:87cf:: with SMTP id v15-v6mr7387373ljj.13.1535641598466; Thu, 30 Aug 2018 08:06:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:dd41:0:0:0:0:0 with HTTP; Thu, 30 Aug 2018 08:06:36 -0700 (PDT) X-Originating-IP: [2620:10d:c090:200::5:2af8] In-Reply-To: References: <1535563287-24803-1-git-send-email-scott.branden@broadcom.com> From: Olof Johansson Date: Thu, 30 Aug 2018 08:06:36 -0700 Message-ID: Subject: Re: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER To: Ard Biesheuvel Cc: Scott Branden , Catalin Marinas , Will Deacon , Arnd Bergmann , BCM Kernel Feedback , Linux ARM Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 29, 2018 at 10:54 PM, Ard Biesheuvel wrote: > On 29 August 2018 at 20:59, Scott Branden wrote: >> 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. > > And these production systems run mainline kernels in a defconfig configuration? > > The simply reality is that the DTB loader has been deprecated for a > good reason: it was only ever intended as a development hack anyway, > and if we need to treat the EFI stub provided DTB as a first class > citizen, there are things we need to fix to make things works as > expected. For instance, GRUB will put a property in the /chosen node > for the initramfs which will get dropped if you boot with dtb=. > > Don't be surprised if some future enhancements of the EFI stub code > depend on !EFI_ARMSTUB_DTB_LOADER. On UEFI systems, DTBs [or ACPI > tables] are used by the firmware to describe itself and the underlying > platform to the OS, and the practice of booting with DTB file images > (taken from the kernel build as well) conflicts with that view. Note > that GRUB still permits you to load DTBs from files (and supports more > sources than just the file system the kernel Image was loaded from). Ard, Maybe a WARN() splat would be more useful as a phasing-out method than removing functionality for them that needs to be reinstated through changing the config? Once the stub and the boot method is there, it's hard to undo as we can see here. Being loud and warn might be more useful, and set a timeline for hard removal (12 months?). Scott; an alternative for you is to do a boot wrapper that bundles a DT and kernel, and boot that instead of the kernel image (outside of the kernel tree). Some 32-bit platforms from Marvell use that. That way the kernel will just see it as a normally passed in DT. -Olof