Lines Matching +full:ubi +full:- +full:volume +full:-
1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Enable UBI - Unsorted block images"
6 UBI is a software layer above MTD layer which admits use of LVM-like
10 (www.linux-mtd.infradead.org).
15 int "UBI wear-leveling threshold"
21 of UBI devices. When this threshold is exceeded, UBI starts performing
26 other flashes which have eraseblock life-cycle 100000 or more.
28 life-cycle less than 10000, the threshold should be lessened (e.g.,
36 This option specifies the maximum bad physical eraseblocks UBI
44 as "1024 * (1 - MinNVB / MaxNVB)", which gives 20 for most NANDs
47 To put it differently, if this value is 20, UBI will try to reserve
50 partition UBI attaches. This means that if you have, say, a NAND
52 MTD partitions of the same size, UBI will reserve 40 eraseblocks when
55 This option can be overridden by the "mtd=" UBI module parameter or
61 bool "UBI Fastmap (Experimental feature)"
64 Important: this feature is experimental so far and the on-flash
67 Fastmap is a mechanism which allows attaching an UBI device
70 The on-flash fastmap contains all information needed to attach
72 attaching by scanning takes long. UBI will not automatically install
73 a fastmap on old images, but you can set the UBI module parameter
74 fm_autoconvert to 1 if you want so. Please note that fastmap-enabled
75 images are still usable with UBI implementations without
77 into one PEB. UBI will reserve PEBs to hold two fastmaps.
84 This option enables gluebi - an additional driver which emulates MTD
85 devices on top of UBI volumes: for each UBI volumes an MTD device is
86 created, and all I/O to this MTD device is redirected to the UBI
87 volume. This is handy to make MTD-oriented software (like JFFS2)
88 work on top of UBI. Do not enable this unless you use legacy
92 bool "Read-only block devices on top of UBI volumes"
96 This option enables read-only UBI block devices support. UBI block
97 devices will be layered on top of UBI volumes, which means that the
98 UBI driver will transparently handle things like bad eraseblocks and
99 bit-flips. You can put any block-oriented file system on top of UBI
100 volumes in read-only mode (e.g., ext4), but it is probably most
101 practical for read-only file systems, like squashfs.
103 When selected, this feature will be built in the UBI driver.
108 bool "Fault injection capability of UBI device"
112 This option enables fault-injection support for UBI devices for
118 tristate "UBI virtual NVMEM"
122 This option enabled an additional driver exposing UBI volumes as NVMEM
123 providers, intended for platforms where UBI is part of the firmware
124 specification and used to store also e.g. MAC addresses or board-
125 specific Wi-Fi calibration data.