[bootlin/training-materials updates] master: Bootloaders: use "DRAM" instead of "RAM" for consistency (cc87d2a4)
Thomas Petazzoni
thomas.petazzoni at bootlin.com
Fri Oct 29 10:46:41 CEST 2021
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/cc87d2a4bddff9aecda5cffc02f70dcaa2624c4a
>---------------------------------------------------------------
commit cc87d2a4bddff9aecda5cffc02f70dcaa2624c4a
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Thu Sep 23 15:14:56 2021 +0200
Bootloaders: use "DRAM" instead of "RAM" for consistency
- And to avoid the ambiguity with SRAM
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
cc87d2a4bddff9aecda5cffc02f70dcaa2624c4a
.../sysdev-bootloaders-sequence.tex | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
index f95e096a..69cadc79 100644
--- a/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
+++ b/slides/sysdev-bootloaders-sequence/sysdev-bootloaders-sequence.tex
@@ -117,12 +117,12 @@
possible in standard boot mode.
\item {\bf U-Boot SPL}: runs from SRAM. Initializes the DRAM,
the NAND or SPI controller, and loads the secondary bootloader
- into RAM and starts it. No user interaction possible.
- \item {\bf U-Boot}: runs from RAM. Initializes some other hardware
+ into DRAM and starts it. No user interaction possible.
+ \item {\bf U-Boot}: runs from DRAM. Initializes some other hardware
devices (network, USB, etc.). Loads the kernel image from
- storage or network to RAM and starts it. Shell with commands
+ storage or network to DRAM and starts it. Shell with commands
provided.
- \item {\bf Linux Kernel}: runs from RAM. Takes over the system
+ \item {\bf Linux Kernel}: runs from DRAM. Takes over the system
completely (the bootloader no longer exists).
\end{itemize}
Note: same process on other Microchip AT91 SoCs, but the
@@ -139,14 +139,14 @@
\footnotesize
\begin{itemize}
\item {\bf ROM Code}: tries to find a valid bootstrap image from
- various storage sources, and load it into RAM. The RAM
+ various storage sources, and load it into DRAM. The DRAM
configuration is described in a CPU-specific header, prepended
to the bootloader image.
- \item {\bf U-Boot}: runs from RAM. Initializes some other hardware
+ \item {\bf U-Boot}: runs from DRAM. Initializes some other hardware
devices (network, USB, etc.). Loads the kernel image from
- storage or network to RAM and starts it. Shell with commands
+ storage or network to DRAM and starts it. Shell with commands
provided. File called \code{u-boot.kwb}.
- \item {\bf Linux Kernel}: runs from RAM. Takes over the system
+ \item {\bf Linux Kernel}: runs from DRAM. Takes over the system
completely (bootloaders no longer exists).
\end{itemize}
\end{columns}
More information about the training-materials-updates
mailing list