Hello, I am trying to add support for my router - Linksys EA-6100 - to OpenWRT. I've successfully compiled an image, but I noticed that doing:
cat /proc/mtd
yields no partitions even though I've defined it in the DTS file corresponding to the router. I've searched around a bit and apparently NAND support has been missing from the kernel.
This patch is missing from the current branch of both LEDE and OpenWRT.
My question is: why is this not included in the upstream branch anymore?
Edit: forgot to mention, I'm running the initramfs and loading the image straight to RAM via tftpboot
Not knowing the exact content of the patch and not being familiar with the ralink platform, it may be due to an upstream insistence that the new SPI NAND framework be used, which is not present in Kernel 4.14 (but will be in 4.19, the next LTS Kernel).
But it requires 4.19 to not have to backport pretty much the whole MTD and SPI subsystems
Please re-spin the patch as soon as we have kernel 4.19 support. The approach was already NAK'ed upstream and I don't see much gain in adding the hack if the next major kernel in OpenWrt will provide a suitable solution.
Hmm. Hopefully, this makes support for NAND chips less hacky and consistent across the board once OpenWRT gets updated to 4.19.
Regardless, I don't see a huge benefit for removing the patch entirely, in fact, looking back at the thread for the Xiaomi Mi Wifi 3, someone else ran into a similar issue. Due to missing NAND support, a fully supported working image was never completed with a couple of people turning to that patch in hopes that it works.
I'll experiment with the patch and see if I can get it working with the current Kernel. If anyone else has a more elegant alternative, I'm all for it.
show the NAND part of your DTS. i've also managed to make system detect NAND in EA2750 using old patch with 4.14 kernel and boot ramdisk but bricked the damn thing before assembled flashable image...
i think this should be named ubi, remove read-only flag and fix length:
reg = <0x5180000 0x2e80000>;
So you say it should be named ubi? But then why is it named "syscfg" in the partition table shown at bootup? The ending address is also less than the starting address, so I'm not too sure about that. I don't have the full bootup log with me, but someone else already posted it on the dd-wrt support tracker. Here
Once I get more time, I'll startup this project again