openwrt/target/linux/ipq40xx/base-files/etc/uci-defaults/05_fix-compat-version

. /lib/functions.sh

case "$(board_name)" in
linksys,ea6350v3|\
linksys,ea8300|\
linksys,mr8300|\
ezviz,cs-w3-wd1200g-eup)
	uci set system.@system[0].compat_version="2.0"
	uci commit system
	;;
esac

exit 0
ipq40xx: unbreak EZVIZ CS-W3-WD1200G EUP on 5.10 with current images, the device is no longer booting. It gets stuck in the bootloader with "Config not available" and drops to the uboot shell. \|flash_type: 0 \|Hit any key to stop autoboot: 0 \|SF: Detected MX25L12805D with page size 4 KiB, total 16 MiB \|Config not availabale \|(IPQ40xx) # This is because the default bootcmd "bootipq" will only read the first four MiB of the kernel image. With 5.10 the gzip'd kernel is slightly larger. So the part of the FIT image which had the configuration is cut off. Hence it can't find it. To update the bootcmd, you have to attach the serial console again and enter the following commands into the boot prompt: # setenv bootcmd "sf probe; sf read 84000000 180000 600000; bootm" # saveenv # run bootcmd This will allow booting kernels with up to six MiB. This also allows us to drop the DEVICE_DTS_CONFIG hack we had to use. Note: uboot doesn't support LZMA. It fails with: "Unimplemented compression type 3" Signed-off-by: Christian Lamparter <chunkeey@gmail.com> 2021-11-28 14:26:18 +00:00			`. /lib/functions.sh`

			`case "$(board_name)" in`
ipq40xx: re-enable EA6350v3, EA8300, MR8300 builds Raise the kernel size from 3 MB to 5 MB for EA6350v3, EA8300 and MR8300, and correspondingly reduce the rootfs size by 2 MB: * modify partition definitions in related .dts files * modify device kernel/image sizes in generic.mk Update to compat-version 2.0 to force factory image usage on sysupgrade, noting the current version 1.1 is an unreleased update for DSA migration. Also update the compat-version message, explaining the need to run one of the following console commands to update U-Boot's kernel-size variable before flashing the OpenWrt factory image. fw_setenv kernsize 500000 # (OpenWrt command line) setenv kernsize 500000 ; saveenv # (U-Boot serial console) Finally, re-enable the 3 devices. Reviewed-by: Robert Marko <robimarko@gmail.com> Tested-by: Nicolas TORMO <badulesia.granieri@gmail.com> # MR8300 Tested-by: Tony Ambardar <itugrok@yahoo.com> # EA6350v3 Signed-off-by: Tony Ambardar <itugrok@yahoo.com> 2022-12-01 04:10:59 +00:00			`linksys,ea6350v3\|\`
			`linksys,ea8300\|\`
			`linksys,mr8300\|\`
ipq40xx: unbreak EZVIZ CS-W3-WD1200G EUP on 5.10 with current images, the device is no longer booting. It gets stuck in the bootloader with "Config not available" and drops to the uboot shell. \|flash_type: 0 \|Hit any key to stop autoboot: 0 \|SF: Detected MX25L12805D with page size 4 KiB, total 16 MiB \|Config not availabale \|(IPQ40xx) # This is because the default bootcmd "bootipq" will only read the first four MiB of the kernel image. With 5.10 the gzip'd kernel is slightly larger. So the part of the FIT image which had the configuration is cut off. Hence it can't find it. To update the bootcmd, you have to attach the serial console again and enter the following commands into the boot prompt: # setenv bootcmd "sf probe; sf read 84000000 180000 600000; bootm" # saveenv # run bootcmd This will allow booting kernels with up to six MiB. This also allows us to drop the DEVICE_DTS_CONFIG hack we had to use. Note: uboot doesn't support LZMA. It fails with: "Unimplemented compression type 3" Signed-off-by: Christian Lamparter <chunkeey@gmail.com> 2021-11-28 14:26:18 +00:00			`ezviz,cs-w3-wd1200g-eup)`
			`uci set system.@system[0].compat_version="2.0"`
			`uci commit system`
			`;;`
			`esac`

			`exit 0`