Lines Matching refs:a

13       Print a list of all of the bad blocks in the current device.
32       If `clean' is specified, a JFFS2-style clean marker is written to
36       a debug option in cmd_nand.c to allow bad blocks to be erased.
45       are marked bad are skipped.  If a page cannot be read because an
56       are marked bad are skipped.  If a page cannot be read because an
59       As JFFS2 skips blocks similarly, this allows writing a JFFS2 image,
67       the NAND flash in a manner identical to the 'nand write' command
84       "addr" in memory.  This is a raw access, so ECC is avoided and the
87       a packed sequence of "data, oob, data, oob, ..." -- no alignment of
121       structs, calls a board init function for a specific device,
128       If a board defines CONFIG_SYS_NAND_SELF_INIT, drivers/mtd/nand/raw/nand.c
130       function is responsible for calling a driver init function for
169       the difference between a U-Boot driver and its Linux counterpart.
171       printing a size summary.  This should also make it easier to
283 There is a driver in drivers/mtd/nand/raw, taken from Linux, that works with
318   automate actions following a nand->write() error. This would e.g. be required
321   Optionally, a second parameter size can be given to test multiple blocks with
322   one call. If size is not a multiple of the NAND's erase size, then the block