arch/riscv/boot.rst

27   * ``$a1`` to contain the address of the devicetree in memory.
41 as per the devicetree specification and/or the UEFI specification.
53 The firmware can pass either a devicetree or ACPI tables to the RISC-V kernel.
55 The devicetree is either passed directly to the kernel from the previous stage
60 this case, a tiny devicetree is still created by the EFI stub. Please refer to
61 "EFI stub and devicetree" section below for details about this devicetree.
86 The UEFI firmware must parse the subnodes of the ``/reserved-memory`` devicetree
87 node and abide by the devicetree specification to convert the attributes of
89 (refer to section "3.5.4 /reserved-memory and UEFI" of the devicetree
100 - ``boot-hartid`` devicetree subnode (**deprecated**).
102 Any new firmware must implement ``RISCV_EFI_BOOT_PROTOCOL`` as the devicetree
110 EFI stub and devicetree
113 When booting with UEFI, the devicetree is supplemented (or created) by the EFI
142 Devicetree mapping via fixmap
148 devicetree. This ensures that the devicetree remains accessible by both virtual