[OpenWrt-Devel] [RFC] ath79: Removal of GL.iNet AR300M NAND Target
lede at allycomm.com
Sun May 19 12:44:18 PDT 2019
I'm in the process of porting the AR750S to the ath79 target with
SPI-NAND support now available on Linux 4.19.
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.
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
While there is support for the GigaDevice E-series SPI NAND already
backported to OpenWrt under Linux 4.19 and I have submitted patches to
support the F-series chips upstream, I have been told that some of the
AR300M units also shipped with Paragon SPI NAND, 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.
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.
From looking at the GL.iNet source, 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.
 3bc8ed91d4 generic-4.19: Backport spi-nand support for GigaDevice A/E
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openwrt-devel