From: Robert Schwebel <r.schwebel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 06/13] doc: unify documentation for 'protect' and 'unprotect'
Date: Tue, 2 Nov 2010 14:10:35 +0100 [thread overview]
Message-ID: <1288703442-5032-7-git-send-email-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <1288703442-5032-1-git-send-email-r.schwebel@pengutronix.de>
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
commands/flash.c | 76 ++++++++++++++++++++++++++++++++----------------------
1 files changed, 45 insertions(+), 31 deletions(-)
diff --git a/commands/flash.c b/commands/flash.c
index 4549f0a..c49de33 100644
--- a/commands/flash.c
+++ b/commands/flash.c
@@ -162,43 +162,57 @@ out:
return ret;
}
-static const __maybe_unused char cmd_protect_help[] =
-"Usage: (un)protect <device> [area]\n"
-"(un)protect a flash device or parts of a device if an area specification\n"
-"is given\n";
+BAREBOX_CMD_HELP_START(protect)
+BAREBOX_CMD_HELP_USAGE("protect <device> [area]\n")
+BAREBOX_CMD_HELP_SHORT("protect a flash device (or parts of a device, if an area is specified)\n")
+BAREBOX_CMD_HELP_END
-BAREBOX_CMD_START(protect)
+BAREBOX_CMD_START(erase)
.cmd = do_protect,
- .usage = "enable FLASH write protection",
+ .usage = "enable flash write protection",
BAREBOX_CMD_HELP(cmd_protect_help)
BAREBOX_CMD_END
-BAREBOX_CMD_START(unprotect)
- .cmd = do_protect,
- .usage = "disable FLASH write protection",
- BAREBOX_CMD_HELP(cmd_protect_help)
-BAREBOX_CMD_END
+/**
+ * @page protect_command
+
+Protect the flash memory behind the device. It depends on the device
+given, what area will be protected. If the device represents the whole
+flash memory the whole memory will be protected. If the device
+represents a partition on a main flash memory, only this partition part
+will be protected.
+
+Refer addpart_command, delpart_command and devinfo_command for partition
+handling.
+
+\todo Rework this documentation, what is an 'area'? Explain more about
+flashes here.
-/** @page protect_command protect Protect a flash memory
- *
- * Usage is: protect \<devicee>
- *
- * Protect the flash memory behind the device. It depends on the device given,
- * what area will be protected. If the device represents the whole flash memory
- * the whole memory will be protected. If the device represents a partition on
- * a main flash memory, only this partition part will be protected.
- *
- * Refer \b addpart, \b delpart and \b devinfo for partition handling.
*/
-/** @page unprotect_command unprotect Unprotect a flash memory
- *
- * Usage is: unprotect \<devicee>
- *
- * Unprotect the flash memory behind the device. It depends on the device given,
- * what area will be unprotected. If the device represents the whole flash memory
- * the whole memory will be unprotected. If the device represents a partition
- * on a main flash memory, only this partition part will be unprotected.
- *
- * Refer \b addpart, \b delpart and \b devinfo for partition handling.
+BAREBOX_CMD_HELP_START(unprotect)
+BAREBOX_CMD_HELP_USAGE("unprotect <device> [area]\n")
+BAREBOX_CMD_HELP_SHORT("unprotect a flash device (or parts of a device, if an area is specified)\n")
+BAREBOX_CMD_HELP_END
+
+BAREBOX_CMD_START(erase)
+ .cmd = do_unprotect,
+ .usage = "enable flash write protection",
+ BAREBOX_CMD_HELP(cmd_unprotect_help)
+BAREBOX_CMD_END
+
+/**
+ * @page unprotect_command
+
+Unprotect the flash memory behind the device. It depends on the device given,
+what area will be unprotected. If the device represents the whole flash memory
+the whole memory will be unprotected. If the device represents a partition
+on a main flash memory, only this partition part will be unprotected.
+
+Refer addpart_command, delpart_command and devinfo_command for partition
+handling.
+
+\todo Rework this documentation, what does it mean?
+
*/
+
--
1.7.2.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-11-02 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 13:10 documentation updates Robert Schwebel
2010-11-02 13:10 ` [PATCH 01/13] doc: remove obsolete link method for arch specification Robert Schwebel
2010-11-02 13:10 ` [PATCH 02/13] doc: unify documentation for 'loadenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 03/13] doc: remove ..., confuses doxygen Robert Schwebel
2010-11-02 13:10 ` [PATCH 04/13] doc: unify documentation for 'mount' Robert Schwebel
2010-11-02 13:10 ` [PATCH 05/13] doc: unify documentation for 'printenv' Robert Schwebel
2010-11-02 13:10 ` Robert Schwebel [this message]
2010-11-02 13:10 ` [PATCH 07/13] doc: unify documentation for 'saveenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 08/13] doc: unify documentation for 'setenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 09/13] doc: remove sh from command documentation Robert Schwebel
2010-11-02 13:10 ` [PATCH 10/13] doc: unify documentation for 'linux16' Robert Schwebel
2010-11-02 13:10 ` [PATCH 11/13] doc: put CPUIMX35 into the right chapter Robert Schwebel
2010-11-02 13:10 ` [PATCH 12/13] doc: put babage board " Robert Schwebel
2010-11-02 13:10 ` [PATCH 13/13] doc: put cupid " Robert Schwebel
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=1288703442-5032-7-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