From: Robert Schwebel <r.schwebel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 3/4] Documentation: user manual: improve tftp description
Date: Wed, 10 Feb 2016 11:07:36 +0100 [thread overview]
Message-ID: <1455098857-25339-3-git-send-email-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <1455098857-25339-1-git-send-email-r.schwebel@pengutronix.de>
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
Documentation/user/barebox.rst | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/user/barebox.rst b/Documentation/user/barebox.rst
index b1f06b0..530693d 100644
--- a/Documentation/user/barebox.rst
+++ b/Documentation/user/barebox.rst
@@ -186,7 +186,9 @@ with U-Boot's 'go' command::
U-Boot: tftp $load_addr barebox.bin
U-Boot: go $load_addr
-With barebox already running on your board, this can be used to chainload another barebox::
+With barebox already running on your board, this can be used to chainload
+another barebox. For instance, if you mounted a TFTP server to ``/mnt/tftp``
+(see :ref:`filesystems_tftp` for how to do that), chainload barebox with::
bootm /mnt/tftp/barebox.bin
--
2.7.0.rc3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-10 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:07 [PATCH 1/4] Documentation: user manual: clarify kconfig+kbuild Robert Schwebel
2016-02-10 10:07 ` [PATCH 2/4] Documentation: filesystems: tftp: bring in line with other filesystem docs Robert Schwebel
2016-02-10 10:07 ` Robert Schwebel [this message]
2016-02-10 10:07 ` [PATCH 4/4] Documentation: networking: improve docs Robert Schwebel
2016-02-10 10:15 ` Steffen Trumtrar
2016-02-11 12:53 ` Sascha Hauer
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=1455098857-25339-3-git-send-email-r.schwebel@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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