Lukas Zeller wrote:
> I really need help to even figure out a feasible idea to fix this, let
> alone implement it in a clean way. What comes to my mind so far is:
> - trying to just zero out enough blocks after the squashfs data in
> `target/linux/bcm27xx/base-files/lib/upgrade/p
development/internal name: Cento
public name: eero (2nd-gen)
model number: J010001
Hardware Info:
SoC : Qualcomm IPQ4019
RAM : 512 MB (Hynix NT5CC256M16ER-EK)
SPI Flash : 8 MB (Winbond W25Q64JVSS)
eMMC Flash : 4 GB (Kingston EMMC0
c888dd0 qca-wireless: ipq40xx: Add BDFs for Eero Cento
Signed-off-by: Connor Northway
---
package/firmware/ipq-wifi/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/firmware/ipq-wifi/Makefile
b/package/firmware/ipq-wifi/Makefile
index 396a4c50b5..aeb690
For quite a while, I've been updating my OpenWrt 22.03 based RPi devices,
configured with sqashfs/f2fs layout (CONFIG_TARGET_ROOTFS_SQUASHFS, rather than
CONFIG_TARGET_ROOTFS_EXT4FS) via sysupgrade with no problems.
However, during a recent update (22.03.5) where the squashfs area only grew
ver
From: Rafał Miłecki
That was a workaround for OpenWrt generation of config files. This patch
was used to postpone returning from probe function until loading
firmware and calling register_wiphy().
All of that is not needed anymore thanks to the ieee80211 hotplug.d
script introduced in the commit
