[PATCH] ramips: support TP-Link EAP615-Wall
sander at svanheule.net
Sat Feb 5 04:30:12 PST 2022
On Sat, 2022-02-05 at 13:36 +0200, Stijn Tintel wrote:
> 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.
You should also be able to use the BLOCKSIZE variable instead of "64k".
The warning you get was patched out previously with target/linux/generic/pending-5.4/411-
mtd-partial_eraseblock_write.patch, but I don't remember seeing that on my own 5.10
Can anyone more experienced with mtd(split) tell if the padding is required here?
More information about the openwrt-devel