Lines Matching full:logical

59  * the %UBI_VTBL_AUTORESIZE_FLG flag set, the amount of available logical
162  * @copy_flag: if this logical eraseblock was copied from another physical
167  * @lnum: logical eraseblock number
169  * @data_size: how many bytes of data this logical eraseblock contains
170  * @used_ebs: total number of used logical eraseblocks in this volume
173  * @data_crc: CRC checksum of the data stored in this logical eraseblock
181  * UBI writes a new VID header to the flash, i.e. when it maps a logical
185  * logical eraseblocks.
188  * corresponding to the same logical eraseblock, i.e., having the same @vol_id
189  * and @lnum values in the volume identifier header. Suppose we have a logical
196  * physical eraseblocks P and P1 corresponding to the same logical eraseblock
200  * 2. From time to time UBI moves logical eraseblocks to other physical
215  * UBI uses the @copy_flag field to indicate that this logical eraseblock is a
241  * The @data_crc field contains the CRC checksum of the contents of the logical
261  * parameter. So, effectively, the @data_pad field reduces the size of logical
329  * the layout volume. The layout volume consists of 2 logical eraseblock, each
334  * If the size of the logical eraseblock is large enough to fit
337  * logical eraseblock divided by sizeof(struct ubi_vtbl_record)).
346  * logical eraseblock size and @alignment. The alignment must be multiple to the