21/01/2020 22:10, Bruno Pena:
Hi everyone,
I was finally able to replicate the issue you are observing.
The problem comes from the fact that the kernel partition on the TP-Link
images is not padded to the write blocksize - which can be observed on
the dmesg from Steve:
[ 0.450987] 0x000000000000-0x0000001a39ea : "kernel"
[ 0.456772] 0x0000001a39ea-0x000000ec0000 : "rootfs"
[...]
> Would any of you be willing to spend some time testing this change on
> your TP-Link?
Hey Bruno,
what you see here, is pretty much OpenWrt standard. It's done this way
to not waste any flash space.
If we would pad the kernel to the erase block boundary, we would lose
flash space, which can't be used for the rootfs. Considering the 0x10000
bytes EB size for the TP-Link device, we would loose 64 KByte in worst case.
Mathias
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
