Posted by Grommish on Aug 17, 2019; 7:31am
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Networks-Shield-Firmware-Upgrade-WIP-tp1726p1844.html

Fantastic!

As I've told Gnomad in the past, my time with the Shield has been limited (Since Feb of this year).  You all have had years of experience with it and will be better able to do the real work of fine tuning.  Besides, you personally have the experience in dealing with the FW updates (along with user8446 and Hans); far beyond what I've done.

My hopes is to get something that is functional, secure, and up to date.  Then maybe we can get people who have tossed the Shield aside to see about bringing it back.  Gnomad had said he gave up on his Shield over a year ago and he can't be the only one.

Any changes you make can either be posted here, Github, or you can email them and I can put it in the image for future users.  I'm still working on the opkg issues, and may have to bite the bullet and revert back to the standard Octeon III CPU define, but I'm not sure exactly what changes that'll have to the kernel.  I'll need to dig deeper and see when I get time.

Also, I need to get more information about the update system.  It calls the sysupdate script, but errors because of some reason - probably I didn't set the device defines up properly.  I wasn't worried about being upstream compliant with OpenWrt - I just wanted it to work.  Since they'll never see it as a legit device anyway, I wasn't overly concerned about just making the code do what I needed it to do, even if it wasn't how OpenWrt does it.