Lines Matching refs:and

12 To make it more clear, here is a small comparison of MTD devices and
15 1 MTD devices represent flash devices and they consist of eraseblocks of
19   eraseblock, write to some offset within an eraseblock, and erase a whole
21   block and write a whole block.
25   typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
27 5 Eraseblocks may become bad (only on NAND flashes) and software should
36 found in drivers/mtd/ubi. UBI is basically a volume management and
41 limitations like wear and bad blocks (items 4 and 5 in the above list).
44 very different and incompatible to JFFS2. The following are the main
47 * JFFS2 works on top of MTD devices, UBIFS depends on UBI and works on
49 * JFFS2 does not have on-media index and has to build it while mounting,
51   information on the flash media and does not require full media scan,
59 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
61 journal and recovers from crashes, ensuring that the on-flash data
65 trees), so the mount time and memory consumption do not linearly depend
91 compr=none              override default compressor and set it to "none"
92 compr=lzo               override default compressor and set it to "lzo"
93 compr=zlib              override default compressor and set it to "zlib"
100 where "X" is UBI device number, "Y" is UBI volume number, and "NAME" is
111 to UBI and mount volume "rootfs":
117 UBIFS documentation and FAQ/HOWTO at the MTD web site: