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 [thread overview] Message-ID: <20201003063725.8698-1-xypron.glpk@gmx.de> (raw) 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(+) -- 2.28.0
WARNING: multiple messages have this Message-ID (diff)
From: Heinrich Schuchardt <xypron.glpk@gmx.de> To: Ard Biesheuvel <ardb@kernel.org> Cc: linux-efi@vger.kernel.org, Atish Patra <atishp@atishpatra.org>, linux-doc@vger.kernel.org, Heinrich Schuchardt <xypron.glpk@gmx.de>, Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, linux-riscv@lists.infradead.org Subject: [PATCH v2 0/2] docs: admin-guide: EFI Boot Stub Date: Sat, 3 Oct 2020 08:37:23 +0200 [thread overview] Message-ID: <20201003063725.8698-1-xypron.glpk@gmx.de> (raw) 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(+) -- 2.28.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2020-10-03 6:38 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-03 6:37 Heinrich Schuchardt [this message] 2020-10-03 6:37 ` [PATCH v2 0/2] docs: admin-guide: EFI Boot Stub Heinrich Schuchardt 2020-10-03 6:37 ` [PATCH v2 1/2] docs: admin-guide: fdt and initrd load in EFI stub Heinrich Schuchardt 2020-10-03 6:37 ` Heinrich Schuchardt 2020-10-03 7:34 ` Atish Patra 2020-10-03 7:34 ` Atish Patra 2020-10-03 8:28 ` Heinrich Schuchardt 2020-10-03 8:28 ` Heinrich Schuchardt 2020-10-03 17:16 ` Atish Patra 2020-10-03 17:16 ` Atish Patra 2020-10-03 6:37 ` [PATCH v2 2/2] docs: admin-guide: EFI stub to main Linux handoff Heinrich Schuchardt 2020-10-03 6:37 ` Heinrich Schuchardt
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=20201003063725.8698-1-xypron.glpk@gmx.de \ --to=xypron.glpk@gmx.de \ --cc=aou@eecs.berkeley.edu \ --cc=ardb@kernel.org \ --cc=atishp@atishpatra.org \ --cc=corbet@lwn.net \ --cc=linux-doc@vger.kernel.org \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.