3 Commits (51d887ba007e56f56f64a4495fc393ae87c7dc97)

Author	SHA1	Message	Date
Gabor Juhos	80a15fe8ad	ar71xx: Fix sysupgrades for Allnet and OpenMesh devices ... Both Allnet and OpenMesh sysupgrade uses fw_setenv from uboot-envtools to change different settings in the uboot environment. uboot-envtools version 2013.01 introduced a filesystem lock "/var/lock/fw_printenv.lock" to guarantee mutually exclusive access to the uboot environment. But the path /var doesn't exist on the sysupgrade ramfs. An upgrade on these devices fails since r36033 ("[package] uboot-envtools: upgrade to version 2013.01.01") with following messages: Error opening lock file /var/lock/fw_printenv.lock failed to update U-Boot environment Creating the "/var/lock" path before running fw_setenv is therefore a requirement unless the locking functionality in fw_setenv is removed or replaced with optional locking. Signed-off-by: Sven Eckelmann <sven@open-mesh.com> Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 38483	11 years ago
Gabor Juhos	4079f3163f	ar71xx: sysupgrade for the ALL0315N ... Signed-off-by: Daniel Golle <dgolle@allnet.de> SVN-Revision: 33285	13 years ago
Gabor Juhos	abffa4ecfb	ar71xx: rename all0258n.sh to allnet.sh ... Signed-off-by: Daniel Golle <dgolle@allnet.de> SVN-Revision: 33284	13 years ago
Gabor Juhos	3a7b12a27d	ar71xx/all0258n: sysupgrade support ... U-Boot on the ALL0258N needs offset, size and md5 for kernel and rootfs to be stored in the U-Boot environment. If the checksums don't match during boot, a failsafe-system is booted instead. This patch adds a board-specific sysupgrade hack for the all0258n which calculates and updates the checksums for the U-Boot environment. Signed-off-by: Daniel Golle <dgolle@allnet.de> SVN-Revision: 28700	13 years ago