aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ar71xx/image/ubinize-wndr4300.ini
diff options
context:
space:
mode:
authorGabor Juhos <juhosg@openwrt.org>2013-11-05 16:31:12 +0000
committerGabor Juhos <juhosg@openwrt.org>2013-11-05 16:31:12 +0000
commit9b0e57fe7facc006306fdda507815b492f6aafb1 (patch)
tree746ebed49e0579977f8895abbdb689550744542c /target/linux/ar71xx/image/ubinize-wndr4300.ini
parent717bb2a9cfa4ea7804db066746c5618aa747d508 (diff)
downloadmaster-187ad058-9b0e57fe7facc006306fdda507815b492f6aafb1.tar.gz
master-187ad058-9b0e57fe7facc006306fdda507815b492f6aafb1.tar.bz2
master-187ad058-9b0e57fe7facc006306fdda507815b492f6aafb1.zip
package/ubox: fix jffs2 handling on MTD devices emulated by gluebi
The jffs2_ready() function in mount_root.c checks the presence of various JFFS2 markers at the start of a given MTD device. The function works on NOR flashes because JFFS2 puts 'cleanmarker' nodes at the start of freshly erased blocks. However if jffs2 is used on a MTD device emulated by the gluebi layer, the 'cleanmarker' nodes are not present and the jffs2_ready() function fails. Update the code to handle jffs2 correctly even on MTD devices emulated by the gluebi layer. Signed-off-by: Gabor Juhos <juhosg@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@38654 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/ar71xx/image/ubinize-wndr4300.ini')
0 files changed, 0 insertions, 0 deletions