Currently I renovate my apartment on the technical site. CAT8 Ethernet (40GBit/s ) I think my home network (Ethernet) infrastructure (Patch cables and wiring) is fast enough for the next 20 years. I also bought a new router, because the old router LinkSys WRT32X lacked ins some functionionality. So I bought a NETGEAR Nighthawk RAX200.
Are there any offical plans to support the RAX200? As far I have seen in the vendor WebUI, there will be OpenWrt (maybe modified) used.
OpenWrt is ONLY a Linux distribution. In the past I have successfully build a Linux distribution from scratch for the purpose of education, so I know what I'm talking about. OpneWrt targets only Router hardware.
Linux MUST support/Implement the devices in the router. NOT OpenWrt. OpenWrt cannot control these devices directly. Only via the Kernel (Linux). Syscall's, ...
Correct, it would have to support it to port OpenWrt for this device, but it doesn't.
There's is only minimal SOC support and zero support for the wireless drivers. Chances for that to change are close to zero as well, Broadcom has repeatedly shown over the last two decades that they don't want to support their softmac/ router wifi chipsets and there is currently no FOSS developer group working on these drivers for the current chipsets either.
While you can play the semantics game, it doesn't change the fact that the chances of this device getting OpenWrt support at all are close to zero.
What you need to realise is that all those OEMs use a heavily mutilated old OpenWrt version that hardware vendors (e.g. Qualcomm) provide. The binary drivers tie into that platform. You cannot just swap out a kernel or driver at will. OpenWrt uses modern kernels (5.10, 5.15) and works with upstream. Vendors 99% of the time do not (check your kernel version for fun).
There are no AX drivers from Broadcom that the FOSS community can use. So it's end of story. With some luck Tomato might support your device at some point e.g.
It's a beginner's mistake to buy stuff first, then hope or expect that OpenWrt will support it. We've all been there.
As software developer maybe. But NOT for a hardware developer (electronic engineer) like me. Also when I delete U-Boot. I can always recover the device. When I delete U-Boot I must open the device and reflash the partions on the FLASH EEPROM's via JTAG, SPI, whatever.. No problem as hardware developer.
I work as embedded hardware AND software developer. I also don't need U-Boot AND/OR Linux. I only need the offical toolchains for the corresponding devices and the full datasheets.