diff options
| author | Wolfgang Denk | 2006-03-06 13:03:37 +0100 |
|---|---|---|
| committer | Wolfgang Denk | 2006-03-06 13:03:37 +0100 |
| commit | bfc81252c0de3bfcf92c7c35bc04341fb33e4e4e (patch) | |
| tree | d2b832bf54040b49a8518b63620f2774398fa8d5 /doc/README.nand | |
| parent | 4e3ccd26925e5ada78dd89779838f052dffe3e67 (diff) | |
Minor code cleanup
Diffstat (limited to 'doc/README.nand')
| -rw-r--r-- | doc/README.nand | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/README.nand b/doc/README.nand index cd7608cf7f5..f2d6a5b1e65 100644 --- a/doc/README.nand +++ b/doc/README.nand @@ -179,7 +179,6 @@ More Definitions: #define NAND_MAX_CHIPS 1 - NOTE: ===== @@ -204,7 +203,7 @@ use JFFS, which has been adopted to use the new NAND, and at the same time use NAND in legacy mode. The breakage will disappear when the board-specific code is changed to the new NAND. -As mentioned above, the legacy code is still used by the DoC subsystem. -The consequence of this is that the legacy NAND can't be removed from -the tree until the DoC is ported to use the new NAND support (or boards +As mentioned above, the legacy code is still used by the DoC subsystem. +The consequence of this is that the legacy NAND can't be removed from +the tree until the DoC is ported to use the new NAND support (or boards with DoC will break). |