openwrt/target/linux/lantiq/base-files/lib/upgrade/platform.sh

PART_NAME=firmware
REQUIRE_IMAGE_METADATA=1

platform_check_image() {
	return 0
}

platform_pre_upgrade() {
	local board=$(board_name)

	case "$board" in
	bt,homehub-v2b|bt,homehub-v3a|bt,homehub-v5a|zyxel,p-2812hnu-f1|zyxel,p-2812hnu-f3)
		nand_do_upgrade $1
		;;
	esac
}

# use default for platform_do_upgrade()

disable_watchdog() {
	killall watchdog
	( ps | grep -v 'grep' | grep '/dev/watchdog' ) && {
		echo 'Could not disable watchdog'
		return 1
	}
}
append sysupgrade_pre_upgrade disable_watchdog
lantiq: add v3.10 patches Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 38031 2013-09-17 21:46:10 +00:00			`PART_NAME=firmware`
lantiq: append metadata to images Signed-off-by: Felix Fietkau <nbd@nbd.name> 2016-11-17 10:41:08 +00:00			`REQUIRE_IMAGE_METADATA=1`
adds new lantiq kernel. once the codebase is fully tested and know to be working on all the devices previously supported by ifxmips, we will drop ifxmips support. SVN-Revision: 24526 2010-12-12 22:57:16 +00:00
			`platform_check_image() {`
lantiq: remove device specific sysupgrade image checks Replaced by image metadata Signed-off-by: Felix Fietkau <nbd@nbd.name> 2016-11-20 19:07:18 +00:00			`return 0`
adds new lantiq kernel. once the codebase is fully tested and know to be working on all the devices previously supported by ifxmips, we will drop ifxmips support. SVN-Revision: 24526 2010-12-12 22:57:16 +00:00			`}`

lantiq: add platform_pre_upgrade for sysupgrade As explained in recent sysupgrade/nand.sh commits, current NAND sysupgrade is a bit misleading because of nand_do_platform_check behavior. It leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. The plan is to have the check function only check the image and nothing else. Then platform code (platform_pre_upgrade) should trigger NAND specific upgrade path. This is what this patch implements. Please note that because of current nand_upgrade_stage1 implementation this patch doesn't change any behaior yet. It only prepares lantiq target for changing nand_do_platform_check (it will be possible after preparing all other targets as well). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 46939 2015-09-15 06:13:07 +00:00			`platform_pre_upgrade() {`
lantiq: remove lantiq_board_name, use the generic function instead Signed-off-by: Felix Fietkau <nbd@nbd.name> 2017-03-17 15:21:30 +00:00			`local board=$(board_name)`
lantiq: add platform_pre_upgrade for sysupgrade As explained in recent sysupgrade/nand.sh commits, current NAND sysupgrade is a bit misleading because of nand_do_platform_check behavior. It leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. The plan is to have the check function only check the image and nothing else. Then platform code (platform_pre_upgrade) should trigger NAND specific upgrade path. This is what this patch implements. Please note that because of current nand_upgrade_stage1 implementation this patch doesn't change any behaior yet. It only prepares lantiq target for changing nand_do_platform_check (it will be possible after preparing all other targets as well). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 46939 2015-09-15 06:13:07 +00:00
			`case "$board" in`
lantiq: use the compatible string as board name Use the first compatible string as board name in userspace. Add the new board name as well as the former used board name to the image metadata to keep compatibilty with already deployed installations. Don't add the former used boardname for boards which exists only in master or evaluation boards. Signed-off-by: Mathias Kresin <dev@kresin.me> 2017-04-08 09:16:21 +00:00			`bt,homehub-v2b\|bt,homehub-v3a\|bt,homehub-v5a\|zyxel,p-2812hnu-f1\|zyxel,p-2812hnu-f3)`
lantiq: add platform_pre_upgrade for sysupgrade As explained in recent sysupgrade/nand.sh commits, current NAND sysupgrade is a bit misleading because of nand_do_platform_check behavior. It leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. The plan is to have the check function only check the image and nothing else. Then platform code (platform_pre_upgrade) should trigger NAND specific upgrade path. This is what this patch implements. Please note that because of current nand_upgrade_stage1 implementation this patch doesn't change any behaior yet. It only prepares lantiq target for changing nand_do_platform_check (it will be possible after preparing all other targets as well). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 46939 2015-09-15 06:13:07 +00:00			`nand_do_upgrade $1`
			`;;`
			`esac`
			`}`

adds new lantiq kernel. once the codebase is fully tested and know to be working on all the devices previously supported by ifxmips, we will drop ifxmips support. SVN-Revision: 24526 2010-12-12 22:57:16 +00:00			`# use default for platform_do_upgrade()`

			`disable_watchdog() {`
			`killall watchdog`
			`( ps \| grep -v 'grep' \| grep '/dev/watchdog' ) && {`
			`echo 'Could not disable watchdog'`
			`return 1`
			`}`
			`}`
			`append sysupgrade_pre_upgrade disable_watchdog`