AR750s Slate dropped from Openwrt tree

brother · 2020-07-09T12:13:10.850Z

Yes, but there is no clean version

alzhao:

BTW, we have 1907 firmware for Slate here https://dl.gl-inet.com/firmware/ar750s/snapshots/ar750s_19.07/

brother · 2020-07-09T12:13:44.785Z

alzhao:

Checking how to do that.

Our patches are here by now https://github.com/gl-inet/openwrt/tree/openwrt-19.07.2

I would appreciate it!

fonix232 · 2020-07-09T17:14:40.698Z

Those are the clean versions.

alzhao:

Checking how to do that.

Our patches are here by now https://github.com/gl-inet/openwrt/tree/openwrt-19.07.2

Any chance you’re going to push the E750 support bits as well?

alzhao · 2020-07-10T02:45:28.214Z

AR750S is dropped because its uboot cannot boot big kernel firmware. We are thinking a way to fix this.

But E750 should not have this problem. We submitted the patch in May but still not yet accepted. We will push.

sfx2000 · 2020-07-10T02:59:32.006Z

While this thread is focused on the AR750S, there is also work on the AR300M-NAND target, not sure if that was pushed thru…

@jeffsf - any comments on AR300M?

fonix232 · 2020-07-10T10:17:56.787Z

alzhao:

But E750 should not have this problem. We submitted the patch in May but still not yet accepted. We will push.

I can’t see the PR in the OpenWrt repos anywhere - nor can I see your changes in the gl-inet/openwrt repo. Could you please link to it?

Johnex · 2020-07-10T11:41:16.021Z

https://patchwork.ozlabs.org/project/openwrt/patch/1588852019-6929-1-git-send-email-luochongjun@gl-inet.com/

brother · 2020-07-10T20:30:56.590Z

alzhao:

AR750S is dropped because its uboot cannot boot big kernel firmware. We are thinking a way to fix this.

Great! If you update the uboot, would you also consider adding the netconsole??

sfx2000 · 2020-07-11T03:08:14.870Z

brother:

Great! If you update the uboot, would you also consider adding the netconsole??

Netconsole is a bit of a security risk - handy yes for development, but not for production…

brother · 2020-07-11T13:46:58.493Z

sfx2000:

Netconsole is a bit of a security risk - handy yes for development, but not for production…

I agree, but so is the uboot web interface…

sfx2000 · 2020-07-11T23:08:20.225Z

Yeah - less risky with the Pepe-2K WebUI though…

NetConsole is a whole different animal

brother · 2020-07-27T00:05:46.577Z

alzhao:

AR750S is dropped because its uboot cannot boot big kernel firmware. We are thinking a way to fix this.

is there any progress on this?

sfx2000 · 2020-07-27T00:12:28.891Z

Working off master… latest log there…

Seem like perhaps yes…

$ git log | grep AR750
ath79: re-enable image generation for GL-AR750S
ath79: improve status LED definitions for GL-AR750
Improve the status LED functionality in GL-AR750
ar71xx: use status led for GL.iNet GL-AR750S
ath79: add support for GL.iNet GL-AR750S when porting the
ath79: GL-AR750S (NOR/NAND): limit factory.img kernel size to 2 MB
The present U-Boot for GL-AR750S has a limit of 2 MB for kernel size.
Fixes: b496a2294c ("ath79: GL-AR750S: provide NAND support; increase kernel to 4 MB")
ath79: GL-AR750S: provide NAND support; increase kernel to 4 MB
The GL.iNet GL-AR750S has been supported by the ar71xx and ath79
The family of GL-AR750S devices on the ath79 platform now includes:
NB: See "ath79: restrict GL-AR750S kernel build-size to 2 MB" which
The GL-AR750S OEM U-Boot allows upload and flashing of either NOR
ath79: GL-AR750S: Add I2C Support
The GL-AR750S has an internal header for I2C.
The GL.iNet AR750S USB and microSD port is currently not working out of
Run-tested-on: GL.iNet AR750S
The GL.iNet AR750S is based around the QCA9563
ath79: align GL-AR750S boardname to other GL.iNet devices
As the official device name is GL-AR750S, rename the board accordingly.
ath79: add support for GL.iNet GL-AR750S
ar71xx: add support for GL.iNet GL-AR750S
This patch adds supports for GL-AR750S.
uboot-envtools: add support for GL.iNet GL-AR750
ar71xx: add support for GL.iNet GL-AR750
GL.iNet GL-AR750 is a small size, dual-band (AC750) router, based on
Qualcomm/Atheros QCA9531 v2 + QCA9887. FCC ID: 2AFIW-AR750.

brother · 2020-07-27T21:37:37.353Z

sfx2000:

Seem like perhaps yes…

no, this was an old commit which was reverted in January:

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=b97247c2e9cd528206dbe5c55055bd913230eba4

@alzhao ??

alzhao · 2020-07-28T04:01:17.475Z

We are working to find a solution, without modifying the bootloader.

m4cman · 2020-08-10T23:47:50.524Z

That’s great news!! I love my ar-750s

Mickey6Pack · 2020-09-21T16:02:46.830Z

Just curious any additional updates?, just got my ar-750s, and hoping it has a fairly long life. But if it is already at it’s EOL from a firmware standpoint may consider something else…

brother · 2020-09-21T16:53:49.900Z

@Mickey6Pack @alzhao Yes, it is possible to build 19.04 from the Gl-inet repo, but it is unfortunate that there is no release build in the whole openwrt repo that we can utilize. While I can build and have, I am a little frustrated that the clean builds are still based on openwrt 18.0x. At the same time, the openwrt dev-community continues to be disfunctional and it is hard for gl-inet to get things committed. It would be good to at least have a new gl-inet clean build based on 19.0x, that way we do not have to rely on having our own build environment just when we want to add a package or two.

Henry_Bruns · 2020-09-24T12:57:35.012Z

brother:

Is GL.iNet going to continue supporting this router to have an Openwrt 19.0x firmware? I am amazed that you all have not re-based by now. It would be better to have newer packages and perhaps even support in the ath79 tree, even if only in the glinet repository…

Any ETA for new firmware based on OpenWRT 19.07.3?

Just wondering if there is any ETA for new firmware based on OpenWRT 19.07.3?

OpenWRT 19.07.4 stable are already out now. On openwrt.org are already available the 19.07.4 for two or more gl routers. See follow:

Time period for WPA3. Better WPA3 beta, than 14 years old and broken PWA2 - #49 by Henry_Bruns

brother · 2021-04-16T14:25:31.201Z

@alzhao
Has there been any further move to fix the situation with building or getting nand support back into the main openwrt tree?