This device was supported earlier with board files. I managed to get it back to working, by booting the kernel over TFTP and just storing the root filesystem in the small flash.
Running LuCI on it is not recommended, as it has only 32MB of RAM, but as your regular bridged AP it work like a charm as a 100MBit only 2g only WiFi AP. Which you may or may not think is worth having. But you can! Details: https://dflund.se/~triad/krad/netgear-wg302/ Signed-off-by: Linus Walleij <linus.wall...@linaro.org> --- Changes in v2: - Added more target patches after finding bugs and missing LEDs in the upstream device tree. - Add a separate patch for OpenWrt LED aliases. - Link to v1: http://lists.openwrt.org/pipermail/openwrt-devel/2024-December/043527.html --- Linus Walleij (4): ixp4xx: Add back support for Netgear WG302 v1 ixp4xx: Support sysupgrade on WG302 v1 ixp4xx: Support single zcom_npe_esa hw address ixp4xx: Add LEDs to supported devices .../linux/ixp4xx/base-files/etc/board.d/02_network | 3 +- .../base-files/lib/preinit/05_set_ether_mac_ixp4xx | 6 +- .../ixp4xx/base-files/lib/upgrade/platform.sh | 27 +++ target/linux/ixp4xx/image/Makefile | 16 ++ .../0007-ARM-dts-ixp4xx-Fix-up-PCI-on-WG302.patch | 40 ++++ ...ARM-dts-ixp4xx-Add-Netgear-WG302-v1-GPIOs.patch | 59 ++++++ .../302-ARM-dts-ixp4xx-OpenWrt-LED-aliases.patch | 228 +++++++++++++++++++++ 7 files changed, 377 insertions(+), 2 deletions(-) --- base-commit: 31e45f62cafbc9361c72d320241e589b31e2b5ed change-id: 20241220-ixp4xx-netgear-wg302-c43d243cc4b4 Best regards, -- Linus Walleij <linus.wall...@linaro.org> _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
