From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: trini@konsulko.com, xypron.glpk@gmx.de, yanhong.wang@starfivetech.com
Cc: Ivan Orlov <ivan.orlov0322@gmail.com>, u-boot@lists.denx.de
Subject: [PATCH] doc: board: starfive: Fix paths in the bash block
Date: Mon, 4 Mar 2024 22:15:32 +0000 [thread overview]
Message-ID: <20240304221532.368453-1-ivan.orlov0322@gmail.com> (raw)
From the current documentation it is not entirely obvious where to take
some of the u-boot build artifacts in order to flash them to the sd
card. Extend the "Program the SD card" block by providing relative paths
to the jh7110-starfive-visionfive-2.dtb and u-boot-spl.bin.normal.out
files.
Add "$(linux_image_dir)/" prefix to the Image.gz and initramfs.cpio.gz
files in order to provide some information about where they could be
taken from.
Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
---
doc/board/starfive/visionfive2.rst | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/board/starfive/visionfive2.rst b/doc/board/starfive/visionfive2.rst
index abda8ac21b..031d66fbfb 100644
--- a/doc/board/starfive/visionfive2.rst
+++ b/doc/board/starfive/visionfive2.rst
@@ -103,15 +103,15 @@ Program the SD card
.. code-block:: bash
- sudo dd if=u-boot-spl.bin.normal.out of=/dev/sdb1
+ sudo dd if=spl/u-boot-spl.bin.normal.out of=/dev/sdb1
sudo dd if=u-boot.itb of=/dev/sdb2
sudo mount /dev/sdb3 /mnt/
- sudo cp u-boot-spl.bin.normal.out /mnt/
+ sudo cp spl/u-boot-spl.bin.normal.out /mnt/
sudo cp u-boot.itb /mnt/
- sudo cp Image.gz /mnt/
- sudo cp initramfs.cpio.gz /mnt/
- sudo cp jh7110-starfive-visionfive-2.dtb /mnt/
+ sudo cp $(linux_image_dir)/Image.gz /mnt/
+ sudo cp $(linux_image_dir)/initramfs.cpio.gz /mnt/
+ sudo cp arch/riscv/dts/jh7110-starfive-visionfive-2.dtb /mnt/
sudo umount /mnt
Booting
--
2.34.1
next reply other threads:[~2024-03-04 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 22:15 Ivan Orlov [this message]
2024-03-05 19:52 ` [PATCH] doc: board: starfive: Fix paths in the bash block Heinrich Schuchardt
2024-03-07 22:36 ` Ivan Orlov
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=20240304221532.368453-1-ivan.orlov0322@gmail.com \
--to=ivan.orlov0322@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yanhong.wang@starfivetech.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox