1config BR2_TARGET_ROOTFS_UBI 2 bool "ubi image containing an ubifs root filesystem" 3 select BR2_TARGET_ROOTFS_UBIFS 4 help 5 Build an ubi image from the ubifs one (with ubinize). 6 7if BR2_TARGET_ROOTFS_UBI 8 9config BR2_TARGET_ROOTFS_UBI_PEBSIZE 10 hex "physical eraseblock size" 11 default 0x20000 12 help 13 Tells ubinize the physical eraseblock (PEB) size of the 14 flash chip the ubi image is created for. The value provided 15 here is passed to the -p/--peb-size option of ubinize. 16 17config BR2_TARGET_ROOTFS_UBI_SUBSIZE 18 int "sub-page size" 19 default 512 20 help 21 Tells ubinize that the flash supports sub-pages and the 22 sub-page size. Use 0 if sub-pages are not supported on flash 23 chip. 24 The value provided here is passed to the -s/--sub-page-size 25 option of ubinize. 26 27config BR2_TARGET_ROOTFS_UBI_USE_CUSTOM_CONFIG 28 bool "Use custom config file" 29 help 30 Select this option to use a custom ubinize configuration file, 31 rather than the default configuration used by Buildroot (which 32 defines a single dynamic volume marked as auto-resize). 33 Passing a custom ubinize configuration file allows you to 34 create several volumes, specify volume types, etc. 35 36 As a convenience, buildroot replaces the string 37 "BR2_ROOTFS_UBIFS_PATH" with the path to the built ubifs file. 38 So the volume defined for the root filesystem can specify the 39 image path as: image=BR2_ROOTFS_UBIFS_PATH 40 41 Buildroot also replaces the string "BINARIES_DIR" with the 42 value of $(BINARIES_DIR), so that it is possible to reference 43 other build artefacts (e.g. to include the kernel in a UBI 44 volume). 45 46config BR2_TARGET_ROOTFS_UBI_CUSTOM_CONFIG_FILE 47 string "Configuration file path" 48 depends on BR2_TARGET_ROOTFS_UBI_USE_CUSTOM_CONFIG 49 help 50 Path to the ubinize configuration file. 51 52config BR2_TARGET_ROOTFS_UBI_OPTS 53 string "Additional ubinize options" 54 help 55 Any additional ubinize options you may want to include. 56 57endif # BR2_TARGET_ROOTFS_UBI 58