Realtek
- For Realtek 802.11 “wireless” chipsets and Realtek SoCs see Realtek
- For Linux drivers for Realtek 802.11 chipsets, see Comparison of open-source wireless drivers and also http://wireless.kernel.org/en/users/Drivers
Lexra
Devices with Lexra SoC
Support status
SoCs of the Lexra Architecture are not supported by OpenWrt since years. It is unlikely that this status changes anytime soon.
Adding support for Lexra
If you want OpenWrt support for a device with a Lexra SoC, you have to add it yourself. See below how to do that.
OpenWrt documentation
External sources
Forum discussions
Quotes
From https://forum.openwrt.org/t/programing-for-new-device/17062/14?u=tmomas:
Lexra is not supported directly by gcc like MIPS, ARM, x86 etc. are. This means that even compiling the first line of C code requires a lot of modification to the system.
Also Realtek does not have good open wifi drivers.
From https://forum.openwrt.org/t/building-openwrt-for-rtl8196c/1379/4?u=tmomas:
The first big problem is that the Lexra CPU core found in these chips isn't one of the platforms directly selectable in gcc. So these third-party projects use a hacked up old version of gcc. And everything kind of falls apart from there. Also open-source drivers for Realtek wifi chips are limited.
From https://openwrt.org/toh/sagem/livebox.2:
It is possible to compile software for Lexra processors using the gnu gcc tools for the MIPS-I R3000 processor. This can be done either by writing an exception trap handler for reserved instructions that detects unaligned load and store instructions and emulates their functionality with shifts and aligned loads and stores or else modifying the compiler so that it does not generate lwl, lwr, swl, and swr instructions. With either of those changes, any C code can run on Lexra processors. Advanced hobbyists might even choose to accelerate their critical inner loops by coding them in assembly code using digital signal processing (DSP) instructions that Lexra implemented as extensions to the MIPS-I instruction set.
From Realtek SoC support in OpenWrt:
In terms of lexra (Realtek's reduced mips ISA) support, there is none - nor anyone actively pushing for it (as in providing patches/ pull requests against current master); chances for this to change are non-zero, but extremely low (once you'd have hypothetical lexra arch/ SOC support, there would still be the problem of the wlan drivers and current hostapd/ nl80211, to drive them reliably in AP mode).
[Disclaimer: I can't speak for the LEDE/ OpenWrt developers]
Personally I don't think lexra will 'ever' be supported in LEDE/ OpenWrt (too different from normal mips, no upstream/ toolchain support at all, very low-end devices, the wlan situation (drivers, AP mode reliability, nl80211 support) is difficult). But effectively all it would need, is someone pushing for it - to provide a (long-term-) manageable pull request with lexra support against OpenWrt/ master, kernel 4.14, musl, hostapd/ nl80211 for the wlan drivers and not too many arch specific changes (so it can be reasonably updated with the rest of OpenWrt and not stay behind).
From https://forum.openwrt.org/t/can-rtl8196c-be-incorporated-into-the-lede/1381:
Afaik there's no upstream support whatsoever towards OpenWrt/LEDE, which is why Realtek devices aren't supported.
Realtek inherited a reduced mips ISA via Lexra, given that this differs from the normal mips ISA, it is quite a bit harder to support - especially lacking active (or any-) upstream development.
From https://forum.openwrt.org/t/can-rtl8196c-be-incorporated-into-the-lede/1381/4?u=tmomas:
I've ported RTL8196C support to LEDE, without wireless support.
All source codes (SPI driver/ethernet driver) were written myself.
https://github.com/hackpascal/lede-rtl8196c 240 (with branch realtek)
But I probably have no time to develop it later.
From https://forum.openwrt.org/t/unsupported-belkin/17252/3?u=tmomas:
The whole target SOC isn't supported at all (search this forum for 'lexra', if you want more details), neither in OpenWrt, nor upstream linux, binutils, gcc, musl, … Adding support for this arch is of course 'possible', but a lot of work - and once there you'd have to deal with getting the wlan drivers to work in AP mode and using contemporary hotapd version, neither will be easy.