@Douglas-Kryder all great information, thank you. Your guess of a new wifi driver release seems realistic. If it doesn't arrive by July (which would be nearly 1 year late) then it probably won't ever come. I'll start testing the official lede builds with Onion packages and report back my findings.
0.1.9 b149 is pretty old. I am one behind at b156, but it has been stable with some bugs worked out. Maybe download and install it, as a number of other packages have been upgraded since the release of b149. Or even to b157. Just a thought.
@Zogg-Baubas Well, it seems my likelihood of doing that is going down fast. I guess I can reformat the drive to ext4? I only went with HFS because I'd been using the drive on a separate machine and it was already formatted (and loaded with a few hundred gig of files). But if that's what I gotta do, I guess that's what I gotta do.
@Armstead-Smith if the individual app is a package in a feed (can be a third party feed like Onion's, or your own), you can build it separately with
This will produce a *.opkg package in bin/packages/mipsel_24kc/FEEDNAME. This can then be copied to the omega2 and installed with opkg.
Setting up your own feed with your own packages is not entirely trivial, but not really difficult either (with some time invested in reading up). I think it's worth doing, to get a nicely organized build.
If all you need is cross-compiling a binary without packaging, you could probably directly use the tools from the toolchain LEDE has build for you in build_dir/toolchain-mipsel_24kc_gcc-5.4.0_musl-1.1.16. You'd need a bunch of environment settings to direct compiler and linker to the correct headers and libraries - but I don't have practical experience with that.
Also, regarding the kernel issues, the Omega's firmware follows the head of the OpenWRT CC repo, we add customizations on top of it. After the campaign, we'll make it a priority to fix that nagging kernel version issue.
Yeah.. I figured it was being put to the back burner but really this is starting to get very frustrating. Standard packages like tinc are available in OpenWRT and so it really should be relatively trivial to compile against the 'Onion' version of the OpenWRT tree. Hell even just putting that source up as a git hub would be enough for people to be able to build packages against the Onion which fit seamlessly into opkg.
Is there a list of what 'customisations' Onion has done to OpenWRT so maybe we can patch an official build with and build from there?
Try the uimage ;) u = micro, iirc, and should provide you bare minimum booting times off the bat (though probably without all the stuff you need listed above).
I think, though, uart is a deferred, with wifi + webserver as an immediate. That would mean that, if you set up your webserver correctly, you can get to minimum boot while you are awaiting the dhcp software and uart to boot. If you make a wifi connection as an initial setup (read: the user is expected to wait for a while on the first initial setup of internet access, with immediate boots thereafter), then your wifi and server can get online fairly quickly I would think. Unless of course, I'm misunderstanding your application.
The reason this approach would work is that minimum response time for a webserver is the key. People/users expect the loading of data to take a while. And, the 'retrieving data log' portion can be a pinwheel to buy you time to load the first time, right? So there is actually a lot you can do to get a product that have nothing to do with overall boot times. . .
So, a bit belatedly, but did ya'll ever get usb-ip ever working? While working on it, I found http://www.virtualhere.com/ which works using the MIPS version of their server on the Onion Omega. Performance doesn't seem particularly amazing, but definitely works, and gives a basic gui for control on clients.