That spectrum is overcrowded and... well, don't advise it. But there are other routers out there that don't have 5GHz. I guess many would be OK without 2.4 
How is this patch coming along? Patchworks shows it still as 'new' but I haven't followed any discussion. Is it available as a patch in openwrt during compile time?
ping. Wonder whether this made it in? Don't know how to interpret NA for State..
Just re-sent an updated version of the series, hoping that it will get more attention, see https://patchwork.ozlabs.org/project/linux-mtd/list/?series=366619
1 Like
Latest seems to be this one.
2024-03-27 Edit: currently this one (which hasn't been accepted yet). Otherwise currently accepted is from December.
One day we'll get UBI to provide NVMEM
Part of Linux v6.9 
And backported to OpenWrt Linux 6.1 and Linux 6.6.
1 Like
You absolute hero.
Is this patch series faithful to the initial intention? Or did you have to make some compromises along the way?
No major changes, functionality as intended and having DT-bindings for UBI is a nice side-product. Still working on providing MTD/UBI upstream folks with (QEMU-based) test-cases, so the new way of attaching UBI via DT can also be part of regular automated tests, which would of course be great.
Having DT-bindings for UBI at all is already great, and would now easily allow defining UBI-related properties (fastmap yes/no, min. number of spare blocks, ...) as well as selecting UBI volumes to be used as ubiblock devices in Device Tree (instead of using kernel cmdline parameters for all that).
Sadly (but somehow also expected) things for NVMEM-on-eMMC are more complicated and less promising at this point, see https://patchwork.kernel.org/project/linux-block/cover/cover.1711048433.git.daniel@makrotopia.org/
But that's another story...
1 Like