Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Heinrich Schuchardt <xypron.glpk@gmx.de>
To:     Ard Biesheuvel <ardb@kernel.org>
Cc:     Jonathan Corbet <corbet@lwn.net>,
        Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>, linux-efi@vger.kernel.org,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-riscv@lists.infradead.org,
        Atish Patra <atishp@atishpatra.org>,
        Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [PATCH v2 0/2] docs: admin-guide: EFI Boot Stub
Date:   Sat,  3 Oct 2020 08:37:23 +0200
Message-Id: <20201003063725.8698-1-xypron.glpk@gmx.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Describe the passing of the device tree and the initial RAM disk to the
EFI Boot Stub.

Describe the handoff to the main Linux kernel. The links given here
provide the necessary information about structures like boot_params that
have to be filled by the EFI stub. So we don't have to describe them in
the admin-guide.

Heinrich Schuchardt (2):
  docs: admin-guide: fdt and initrd load in EFI stub
  docs: admin-guide: EFI stub to main Linux handoff

 Documentation/admin-guide/efi-stub.rst | 47 ++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)

=2D-
2.28.0