From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 8/8] tftp: update doxygen information
Date: Thu, 24 Jun 2010 11:35:08 +0200 [thread overview]
Message-ID: <1277372108-30332-9-git-send-email-s.hauer@pengutronix.de> (raw)
In-Reply-To: <1277372108-30332-1-git-send-email-s.hauer@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
net/tftp.c | 21 +++++++++++++--------
1 files changed, 13 insertions(+), 8 deletions(-)
diff --git a/net/tftp.c b/net/tftp.c
index 000d0cf..c0d3278 100644
--- a/net/tftp.c
+++ b/net/tftp.c
@@ -376,16 +376,21 @@ BAREBOX_CMD_END
/**
* @page tftp_command tftp
*
- * Usage is: tftp \<filename\> [\<localfilename\>]
+ * Usage:
+ * tftp \<remotefilename\> [\<localfilename\>]
*
- * Load a file via network using BootP/TFTP protocol. The loaded file you
- * can find after download in you current ramdisk. Refer \b ls command.
+ * or
*
- * \<localfile> can be the local filename only, or also a device name. In the
- * case of a device name, the will gets stored there. This works also for
- * partitions of flash memory. Refer \b erase, \b unprotect for flash
- * preparation.
+ * tftp -p \<localfilename\> [\<remotefilename\>]
*
- * Note: This command is available only, if enabled in the menuconfig.
+ * Load a file from a tftp server or upload a file to a tftp server if
+ * the -p option is given. The second file argument can be skipped in
+ * which case the first filename is used (without the directory part).
+ *
+ * \<localfile> can be the local filename or a device file under /dev.
+ * This also works for flash memory. Refer to \b erase, \b unprotect for
+ * flash preparation.
+ *
+ * Note: This command is available only if enabled in menuconfig.
*/
--
1.7.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-06-24 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 9:35 more network patches Sascha Hauer
2010-06-24 9:35 ` [PATCH 1/8] tftp: remove unused variables Sascha Hauer
2010-06-24 9:35 ` [PATCH 2/8] add progression bar function Sascha Hauer
2010-06-24 9:35 ` [PATCH 3/8] cfi flash driver: Use generic " Sascha Hauer
2010-06-24 9:35 ` [PATCH 4/8] tftp: use generic progression bar Sascha Hauer
2010-06-24 9:35 ` [PATCH 5/8] tftp: Add push support Sascha Hauer
2010-06-24 9:35 ` [PATCH 6/8] nfs: Use generic progression bar Sascha Hauer
2010-06-24 9:35 ` [PATCH 7/8] nfs: resend requests after timeout Sascha Hauer
2010-06-24 9:35 ` Sascha Hauer [this message]
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=1277372108-30332-9-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@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