aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic/patches-3.10/040-UBI-R-O-block-driver-on-top-of-UBI-volumes.patch
diff options
context:
space:
mode:
authorJohn Crispin <blogic@openwrt.org>2014-06-11 12:59:10 +0000
committerJohn Crispin <blogic@openwrt.org>2014-06-11 12:59:10 +0000
commit41aefc93320d42ff4ae8baab83f61b60c6e65d2b (patch)
tree28b5cc56bd1387953c7206e3e5924fe7a120d186 /target/linux/generic/patches-3.10/040-UBI-R-O-block-driver-on-top-of-UBI-volumes.patch
parentf9d01db1cd353a17ffee483ff5d225b8f5e7b0ba (diff)
downloadupstream-41aefc93320d42ff4ae8baab83f61b60c6e65d2b.tar.gz
upstream-41aefc93320d42ff4ae8baab83f61b60c6e65d2b.tar.bz2
upstream-41aefc93320d42ff4ae8baab83f61b60c6e65d2b.zip
kernel: rootfs auto-mount on ubi
Similar to the rootfs hacks on NOR flash devices, this series introduces support for auto-attaching (ubi device), auto-creating (ubiblock device) and mounting the "rootfs" (ubifs or squashfs) volume. This is needed so OpenWrt can start without relying on the bootloader to pass the ubi.mtd, ubi.block, rootfs and rootfstype parameters, but instead auto-detect the root filesystem according to a simple convention. OpenWrt-specific: 490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch 491-ubi-auto-create-ubiblock-device-for-rootfs.patch 492-try-auto-mounting-ubi0-rootfs-in-init-do_mounts.c.patch 493-ubi-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch sent upstream: 552-ubifs-respect-silent-mount-flag.patch http://lists.infradead.org/pipermail/linux-mtd/2014-May/053893.html v2: actually retry with MS_RDONLY when mounting read-only ubifs root Signed-off-by: Daniel Golle <daniel@makrotopia.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@41119 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/generic/patches-3.10/040-UBI-R-O-block-driver-on-top-of-UBI-volumes.patch')
0 files changed, 0 insertions, 0 deletions