diff options
| author | Christian Lamparter <chunkeey@gmail.com> | 2022-02-06 14:24:32 +0100 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2022-02-06 17:11:20 +0100 |
| commit | f6a01d7f5c3d945f031cf24ab66066806dd62db3 (patch) | |
| tree | 455e49ed770e1306eefe9a9c8c97bfd75263415b /package/base-files/image-config.in | |
| parent | 4d904524effc9eb0cc5094574c55d3a520803223 (diff) | |
| download | upstream-f6a01d7f5c3d945f031cf24ab66066806dd62db3.tar.gz upstream-f6a01d7f5c3d945f031cf24ab66066806dd62db3.tar.bz2 upstream-f6a01d7f5c3d945f031cf24ab66066806dd62db3.zip | |
ipq806x: convert TP-Link Archer VR2600v to denx,uimage
The recent device-tree modification that added pre-cal
nvmem-cells pushed the device's kernel+dtb over the
allotted 3072k KERNEL_SIZE.
> WARNING: Image file tplink_vr2600v-uImage is too big: 3147214 > 3145728
There was a previous kernel partition size upgrade:
commit 0c967d92b3d9 ("ipq806x: increase kernel partition size for the TP-Link Archer VR2600v")
It has been seemingly upgraded from a 2048k KERNEL_SIZE in the past.
The commit talks about using the MTD_SPLIT_TPLINK_FW. But looking at
the image make recipe, there is no code that adds a TPLINK header.
So instead the board will use "denx,umimage". This requires
MTD_SPLIT_UIMAGE_FW, but this is present thanks to some NEC devices.
(Maybe the MTD_CONFIG_ARGS can be removed as well? But it could be
there because of the padding at the beginning. This needs testing.)
Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
Diffstat (limited to 'package/base-files/image-config.in')
0 files changed, 0 insertions, 0 deletions