auracaster/sw_openocd
3
0
Fork 0
forked from auracaster/openocd
Code Pull Requests Activity

NAND: help/usage/doc updates

Browse Source 
Usage messages should use the same EBNF as the User's Guide;
no angle brackets.  Be more complete too ... some params were
missing.  Improve and correct various helptexts.

Make user's guide refer to the NAND "driver" name, not the
controller name; that's a bit more precise.

Don't use "&function"; its name is its address.  Line up struct
initializers properly.  Remove some blank lines.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
This commit is contained in:
David Brownell
2010-01-08 23:18:46 -08:00
parent ae71005929
commit 2a76c1bcf9
4 changed files with 53 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/openocd.texi
View File

@@ -4673,7 +4673,7 @@ NAND chips must be declared in configuration scripts,
plus some additional configuration that's done after
OpenOCD has initialized.
@deffn {Config Command} {nand device} name controller target [configparams...]
@deffn {Config Command} {nand device} name driver target [configparams...]
Declares a NAND device, which can be read and written to
after it has been configured through @command{nand probe}.
In OpenOCD, devices are single chips; this is unlike some
@@ -4688,8 +4688,8 @@ configuration files, not interactively.
@itemize @bullet
@item @var{name} ... may be used to reference the NAND bank
in other commands.
@item @var{controller} ... identifies the controller driver
in most other NAND commands. A number is also available.
@item @var{driver} ... identifies the NAND controller driver
associated with the NAND device being declared.
@xref{NAND Driver List}.
@item @var{target} ... names the target used when issuing