Changes between Version 9 and Version 10 of linux/ubi


Ignore:
Timestamp:
10/09/2018 04:02:15 PM (12 days ago)
Author:
Cale Collins
Comment:

relocated Creating your own .ubifs file section

Legend:

Unmodified
Added
Removed
Modified
  • linux/ubi

    v9 v10  
    105105}}}
    106106
     107=== Creating your own .ubifs file
     108{{{#!bash
     109sudo mkfs.ubifs -d /your/rootfs/ -F -m 4096 -e 248KiB -c 8124 -x zlib -o A_large.ubifs
     110}}}
     111
     112Essentials:
     113
     114 * **-r** Build file system from directory DIR
     115 * **-F**  The -F option causes mkfs.ubifs to set a special flag in the superblock, which triggers a "free space fixup" procedure in the kernel the very first time the filesystem is mounted. This fixup procedure involves finding all empty pages in the UBIFS file system and re-erasing them. This ensures that NAND pages which contain all 0xFF data get fully erased, which removes any problematic non-0xFF data from their OOB areas.
     116 * **-m**  Minimum I/O unit size
     117 * **-e**  Logical erase block size
     118 * **-c** Maximum logical erase block count
     119 * **-x** Compression type - "lzo", "favor_lzo", "zlib" or "none" (default: "lzo")
     120 * **-o** Output to FILENAME
     121 * **-h** Help, provides full list of options
    107122
    108123== Working with a UBI in Linux OS (extracting or manipulating contents) ==
     
    211226
    212227
     228
     229
    213230=== On a target board with NAND FLASH ===
    214231[=#ubiontarget]
     
    325342Use the information in the section above for examples on how to load data in uboot from various sources such as network, mmc, usb.
    326343
    327 === Creating your own .ubifs file
    328 {{{#!bash
    329 sudo mkfs.ubifs -d /your/rootfs/ -F -m 4096 -e 248KiB -c 8124 -x zlib -o A_large.ubifs
    330 }}}
    331 
    332 Essentials:
    333 
    334  * **-r** Build file system from directory DIR
    335  * **-F**  The -F option causes mkfs.ubifs to set a special flag in the superblock, which triggers a "free space fixup" procedure in the kernel the very first time the filesystem is mounted. This fixup procedure involves finding all empty pages in the UBIFS file system and re-erasing them. This ensures that NAND pages which contain all 0xFF data get fully erased, which removes any problematic non-0xFF data from their OOB areas.
    336  * **-m**  Minimum I/O unit size
    337  * **-e**  Logical erase block size
    338  * **-c** Maximum logical erase block count
    339  * **-x** Compression type - "lzo", "favor_lzo", "zlib" or "none" (default: "lzo")
    340  * **-o** Output to FILENAME
    341  * **-h** Help, provides full list of options
     344
    342345