Sven Eckelmann 78a5d25dca ar71xx: Skip more hashed blocks for OM2P(-HS) 64k variant ... The OM2P(-HS)v4 got a variant which uses a slightly different flash. The standard versions used a flash with 256KB blocks which is no longer available. The replacement flash uses a flash with 64K blocks. The padding for the image rootfs is already for 64K and 256K and thus can be flashed on the device without any problems. Unfortunately, the bootloader will check $rootfs_size (rounded down to the nearest 64k block) minus 1x 64k. But it is now possible that the new JFFS2 rootfs_data starts even earlier and modifies the checked region. The check will then fail and the backup image (when available) will be booted. Just setting it to the same number of skipped blocks as other 64K models avoids this problem. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>		2018-09-10 10:01:58 +02:00
..
config
flashing
arm-magic.sh
brcmImage.pl
bundle-libraries.sh
checkpatch.pl
clang-gcc-wrapper
clean-package.sh
cleanfile
cleanpatch
combined-ext-image.sh
combined-image.sh
config.guess
config.rpath
config.sub
deptest.sh
diffconfig.sh
dl_cleanup.py
dl_github_archive.py
download.pl
env
ext-toolchain.sh
feeds
fixup-makefile.pl
gen_image_generic.sh
gen-dependencies.sh
get_source_date_epoch.sh
getver.sh
ipkg-build
ipkg-make-index.sh
kconfig.pl
make-ipkg-dir.sh
md5sum
metadata.pm
mkhash.c
mkits.sh
om-fwupgradecfg-gen.sh
package-metadata.pl
pad_image
patch-kernel.sh
patch-specs.sh
portable_date.sh
qemustart
redboot-script.pl
relink-lib.sh
remote-gdb
rstrip.sh
slugimage.pl
srecimage.pl
strip-kmod.sh
symlink-tree.sh
sysupgrade-tar.sh
target-metadata.pl
time.pl
timestamp.pl
ubinize-image.sh