summaryrefslogtreecommitdiff
path: root/doc/usage/blkmap.rst
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2025-04-25 13:11:40 -0600
committerTom Rini <trini@konsulko.com>2025-04-25 13:11:40 -0600
commit7a9c9b5655646c229e4300c24b0b85b51308795e (patch)
tree146f366ba7bf516e7035faaaa356d49aac81ff86 /doc/usage/blkmap.rst
parent9d3f1ebaf8751f0287b5d02158cc706435f8fb19 (diff)
parent0ded46384952ab74eb7dd54515a3e23bcbb9ca88 (diff)
Merge tag 'efi-2025-07-rc1-3' of https://source.denx.de/u-boot/custodians/u-boot-efi
Pull request efi-2025-07-rc1-3 Documentation: * add documentation for the DeepComputing FML13V01 * fix typos UEFI: * build with HII configuration protocol * print image load address in StartImage Boards: * qemu-riscv raise CONFIG_NR_DRAM_BANKS * add support for the DeepComputing FML13V01 board via starfive_visionfive2_defconfig * add UNIT_TESTS to big-endian Malta boards
Diffstat (limited to 'doc/usage/blkmap.rst')
-rw-r--r--doc/usage/blkmap.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/usage/blkmap.rst b/doc/usage/blkmap.rst
index 75f736c259f..4e9091e8ffa 100644
--- a/doc/usage/blkmap.rst
+++ b/doc/usage/blkmap.rst
@@ -39,7 +39,7 @@ network. Getting the image to the target is easy enough:
dhcp ${ramdisk_addr_r} rootfs.ext4
-But now we are faced with a predicament: how to we extract the kernel
+But now we are faced with a predicament: how do we extract the kernel
image? Block maps to the rescue!
We start by creating a new device: