summaryrefslogtreecommitdiff
path: root/target/linux/generic/patches-3.6/910-kobject_uevent.patch
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2014-06-11 12:59:10 +0000
committerJohn Crispin <john@openwrt.org>2014-06-11 12:59:10 +0000
commitacbcd5f5b5465b28f966abd7f8da98062ba09935 (patch)
treeae09eb2973f52f35af1b42a944006ebd9b7ebd99 /target/linux/generic/patches-3.6/910-kobject_uevent.patch
parentd494983d020035cacd8d8023afad22d2761fa7fc (diff)
downloadmtk-20170518-acbcd5f5b5465b28f966abd7f8da98062ba09935.zip
mtk-20170518-acbcd5f5b5465b28f966abd7f8da98062ba09935.tar.gz
mtk-20170518-acbcd5f5b5465b28f966abd7f8da98062ba09935.tar.bz2
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> SVN-Revision: 41119
Diffstat (limited to 'target/linux/generic/patches-3.6/910-kobject_uevent.patch')
0 files changed, 0 insertions, 0 deletions