diff options
| author | Gabor Juhos <juhosg@openwrt.org> | 2013-11-05 16:31:12 +0000 |
|---|---|---|
| committer | Gabor Juhos <juhosg@openwrt.org> | 2013-11-05 16:31:12 +0000 |
| commit | 2d31dc039ac69bca62edd9f915834f5e7ebe4d25 (patch) | |
| tree | 911d03985a35ad34c6e916d2098ce69665d8cc0f /scripts/patch-kernel.sh | |
| parent | 35656042f1cd457819a75c980613634b494a7e70 (diff) | |
| download | mtk-20170518-2d31dc039ac69bca62edd9f915834f5e7ebe4d25.zip mtk-20170518-2d31dc039ac69bca62edd9f915834f5e7ebe4d25.tar.gz mtk-20170518-2d31dc039ac69bca62edd9f915834f5e7ebe4d25.tar.bz2 | |
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>
SVN-Revision: 38654
Diffstat (limited to 'scripts/patch-kernel.sh')
0 files changed, 0 insertions, 0 deletions