tplink-safeloader: don't end-pad sysupgrade file

To ensure the stock rootfs ends up at the correct offset, the preceding
kernel partition is padded with 0xff, corresponding to erased flash.
Since on sysupgrade all the required flash space is anyway rased before
writing the new image, it is not necessary to also pad after the second
and last part of the generated image. This can reduce the generated
image size by several MiB.

Signed-off-by: Sander Vanheule <sander@svanheule.net>

diff --git a/src/tplink-safeloader.c b/src/tplink-safeloader.c
index 5b19e8726821f86e3dfa17f035956cbe2604b4d3..05b7ca17f7864f9546cc5c96ba28803100c8b931 100644 (file)
--- a/src/tplink-safeloader.c
+++ b/src/tplink-safeloader.c
@@ -4071,7 +4071,6 @@ static void convert_firmware(const char *input, const char *output)
        /* write file-system behind os_image */
        fseek(output_file, flash_file_system->base - flash_os_image->base, SEEK_SET);
        write_partition(input_file, firmware_offset, fwup_file_system, output_file);
-       write_ff(output_file, flash_file_system->size - fwup_file_system->size);
 
        fclose(output_file);
        fclose(input_file);