[OpenWrt-Devel] [RFC] ath79: Removal of GL.iNet AR300M NAND Target

[Marty E. Plummer]

On Sun, May 19, 2019 at 12:44:18PM -0700, Jeff Kletsky wrote:
> I'm in the process of porting the AR750S to the ath79 target with
> SPI-NAND support now available on Linux 4.19[1].
> 
> From what I can tell, the AR300M (NAND) target, while it builds,
> does not provide a functional image with either Linux 4.14 or 4.19
> as there has not been and is not yet an applicable SPI-NAND driver
> built by OpenWrt[2].
> 
> While the ar71xx target had various patches to provide an SPI-attached
> NAND driver, at least as I understand it, these were rejected for the
> ath79 target in favor of the upstream SPI-NAND framework that would
> become available[2,3].
> 
> While there is support for the GigaDevice E-series SPI NAND already
> backported to OpenWrt under Linux 4.19[4] and I have submitted patches to
> support the F-series chips upstream[5], I have been told that some of the
> AR300M units also shipped with Paragon SPI NAND[6], for which there is no
> upstream driver support at this time.
> 
> 
> 
> As there is no bootable image produced, I would like to remove
> the AR300M (NAND) target from the ath79 tree at this time. The AR300M
> would remain on the ath79 generic (NOR) target.
> 
> The intention is that the AR300M (NAND) would be reinstated once
> proper driver support is available.
> 
> 
> 
> ======================
> If you have objections to this course of action, please let me know.
> ======================
> 
Nah. Worst case is we have to dig the commmit log and pull the data back
out. That's the great thing about git.
> 
> 
> Also, if you have an AR300M with the Paragon SPI NAND that you would
> be able to assist me in testing development of an upstream-supported
> driver, please also let me know.
> 
I do believe my particular ar300m is paragon based, and I'm more than
willing to assist wherever I can. I was under the impression that
bbrezelion or however you spell it was working on a generic spi-nand
driver?
> From looking at the GL.iNet source[7], I would expect to see `dmesg` on
> an OEM or image built from their sources to display a line containing
> 
>     spi-nand: Paragon SPI NAND was found.
> 
> These are probably older-production units.
> 
> 
> 
> Jeff
> 
> 
> ---
> 
> [1] http://patchwork.ozlabs.org/project/openwrt/list/?series=107880
> 
> [2] http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015604.html
>     http://lists.infradead.org/pipermail/openwrt-devel/2019-January/015606.html
> 
> [3] https://github.com/openwrt/openwrt/pull/1428#issuecomment-441594401
> 
> [4] 3bc8ed91d4 generic-4.19: Backport spi-nand support for GigaDevice A/E
> 
> [5] http://patchwork.ozlabs.org/project/linux-mtd/list/?series=107874
> 
> [6] http://www.xtxtech.com/upfile/2016082517274590.pdf
> 
> [7] <https://github.com/gl-inet/openwrt/blob/develop/target/linux/ar71xx/patches-4.9/491-mtd-spi-nand-driver.patch#L2678>
> 

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel