diff options
author | Christian Lamparter <chunkeey@gmail.com> | 2021-11-28 15:26:18 +0100 |
---|---|---|
committer | Christian Lamparter <chunkeey@gmail.com> | 2021-12-04 00:36:47 +0100 |
commit | 45eb57f12f3a128a1822a20b7e536527ab92ca67 (patch) | |
tree | 6fe1a8a9342f040bb9df3e961f58351a60174b6d /target/linux/omap | |
parent | eb20a1b8bb631084b9a70126eac2a6e32c3f3565 (diff) | |
download | upstream-45eb57f12f3a128a1822a20b7e536527ab92ca67.tar.gz upstream-45eb57f12f3a128a1822a20b7e536527ab92ca67.tar.bz2 upstream-45eb57f12f3a128a1822a20b7e536527ab92ca67.zip |
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>
Diffstat (limited to 'target/linux/omap')
0 files changed, 0 insertions, 0 deletions