On 4/02/2022 20:05, Stijn Tintel wrote: >>> + DEVICE_MODEL := EAP615-Wall >>> + DEVICE_VARIANT := v1 >>> + DEVICE_PACKAGES := kmod-mt7915e >>> + TPLINK_BOARD_ID := EAP615-WALL-V1 >>> + KERNEL := kernel-bin | lzma | fit lzma $$(KDIR)/image-$$(firstword >>> $$(DEVICE_DTS)).dtb | pad-to 64k >>> + KERNEL_INITRAMFS := kernel-bin | lzma | fit lzma >>> $$(KDIR)/image-$$(firstword >>> $$(DEVICE_DTS)).dtb with-initrd | pad-to 64k >> Is the 'pad-to 64k' required? mtdsplit can split at arbitrary boundaries, so >> I think the >> padding here isn't very useful. The other device with FIT images on mt7621 >> also don't add >> padding to the kernel. > Removed.
Removing the padding causes this logging line during boot: [ 0.712046] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only While it doesn't cause any real issues, I prefer to not have this message. The datasheet leaves me clueless about the erase block size, but in sysfs I can find 64k, so I'm going to add back pad-to 64k to KERNEL. Stijn _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
