DocBook: fix mtdnand typos · tjh.dev/kernel@8011b3c

+15 -15

1 changed file

expand all

Documentation

DocBook

mtdnand.tmpl

+15 -15

Documentation/DocBook/mtdnand.tmpl

··· 91 91 <listitem><para> 92 92 [MTD Interface]</para><para> 93 93 These functions provide the interface to the MTD kernel API. 94 - They are not replacable and provide functionality 94 + They are not replaceable and provide functionality 95 95 which is complete hardware independent. 96 96 </para></listitem> 97 97 <listitem><para> ··· 100 100 </para></listitem> 101 101 <listitem><para> 102 102 [GENERIC]</para><para> 103 - Generic functions are not replacable and provide functionality 103 + Generic functions are not replaceable and provide functionality 104 104 which is complete hardware independent. 105 105 </para></listitem> 106 106 <listitem><para> 107 107 [DEFAULT]</para><para> 108 108 Default functions provide hardware related functionality which is suitable 109 109 for most of the implementations. These functions can be replaced by the 110 - board driver if neccecary. Those functions are called via pointers in the 110 + board driver if necessary. Those functions are called via pointers in the 111 111 NAND chip description structure. The board driver can set the functions which 112 112 should be replaced by board dependent functions before calling nand_scan(). 113 113 If the function pointer is NULL on entry to nand_scan() then the pointer ··· 264 264 is set up nand_scan() is called. This function tries to 265 265 detect and identify then chip. If a chip is found all the 266 266 internal data fields are initialized accordingly. 267 - The structure(s) have to be zeroed out first and then filled with the neccecary 267 + The structure(s) have to be zeroed out first and then filled with the necessary 268 268 information about the device. 269 269 </para> 270 270 <programlisting> ··· 327 327 <sect1 id="Exit_function"> 328 328 <title>Exit function</title> 329 329 <para> 330 - The exit function is only neccecary if the driver is 330 + The exit function is only necessary if the driver is 331 331 compiled as a module. It releases all resources which 332 332 are held by the chip driver and unregisters the partitions 333 333 in the MTD layer. ··· 494 494 in this case. See rts_from4.c and diskonchip.c for 495 495 implementation reference. In those cases we must also 496 496 use bad block tables on FLASH, because the ECC layout is 497 - interferring with the bad block marker positions. 497 + interfering with the bad block marker positions. 498 498 See bad block table support for details. 499 499 </para> 500 500 </sect2> ··· 542 542 <para> 543 543 nand_scan() calls the function nand_default_bbt(). 544 544 nand_default_bbt() selects appropriate default 545 - bad block table desriptors depending on the chip information 545 + bad block table descriptors depending on the chip information 546 546 which was retrieved by nand_scan(). 547 547 </para> 548 548 <para> ··· 554 554 <sect2 id="Flash_based_tables"> 555 555 <title>Flash based tables</title> 556 556 <para> 557 - It may be desired or neccecary to keep a bad block table in FLASH. 557 + It may be desired or necessary to keep a bad block table in FLASH. 558 558 For AG-AND chips this is mandatory, as they have no factory marked 559 559 bad blocks. They have factory marked good blocks. The marker pattern 560 560 is erased when the block is erased to be reused. So in case of ··· 565 565 of the blocks. 566 566 </para> 567 567 <para> 568 - The blocks in which the tables are stored are procteted against 568 + The blocks in which the tables are stored are protected against 569 569 accidental access by marking them bad in the memory bad block 570 570 table. The bad block table management functions are allowed 571 - to circumvernt this protection. 571 + to circumvent this protection. 572 572 </para> 573 573 <para> 574 574 The simplest way to activate the FLASH based bad block table support ··· 592 592 User defined tables are created by filling out a 593 593 nand_bbt_descr structure and storing the pointer in the 594 594 nand_chip structure member bbt_td before calling nand_scan(). 595 - If a mirror table is neccecary a second structure must be 595 + If a mirror table is necessary a second structure must be 596 596 created and a pointer to this structure must be stored 597 597 in bbt_md inside the nand_chip structure. If the bbt_md 598 598 member is set to NULL then only the main table is used ··· 666 666 <para> 667 667 For automatic placement some blocks must be reserved for 668 668 bad block table storage. The number of reserved blocks is defined 669 - in the maxblocks member of the babd block table description structure. 669 + in the maxblocks member of the bad block table description structure. 670 670 Reserving 4 blocks for mirrored tables should be a reasonable number. 671 671 This also limits the number of blocks which are scanned for the bad 672 672 block table ident pattern. ··· 1068 1068 <chapter id="filesystems"> 1069 1069 <title>Filesystem support</title> 1070 1070 <para> 1071 - The NAND driver provides all neccecary functions for a 1071 + The NAND driver provides all necessary functions for a 1072 1072 filesystem via the MTD interface. 1073 1073 </para> 1074 1074 <para> 1075 - Filesystems must be aware of the NAND pecularities and 1075 + Filesystems must be aware of the NAND peculiarities and 1076 1076 restrictions. One major restrictions of NAND Flash is, that you cannot 1077 1077 write as often as you want to a page. The consecutive writes to a page, 1078 1078 before erasing it again, are restricted to 1-3 writes, depending on the ··· 1222 1222 #define NAND_BBT_VERSION 0x00000100 1223 1223 /* Create a bbt if none axists */ 1224 1224 #define NAND_BBT_CREATE 0x00000200 1225 - /* Write bbt if neccecary */ 1225 + /* Write bbt if necessary */ 1226 1226 #define NAND_BBT_WRITE 0x00001000 1227 1227 /* Read and write back block contents when writing bbt */ 1228 1228 #define NAND_BBT_SAVECONTENT 0x00002000

Configure Feed

Configure Feed