@Chris-Stratton Chris, thanks for the reply and educating me on some of the limitations. As for why htop - I wanted to practice on something and its one of my go-to utilities, so this was more of a test run.
Looks like this is the most recent thread on GPIO Interrupts. What's the current status on GPIO interrupt support on the Omega2?
what are the typical latencies associated with the sysfs method?
are there any advantages for the kmod-gpio-irq path?
if so, is there a reliable way to use kmod-gpio-irq on the Omega2 or is it likely to end in the dead-ends reported in this thread?
@Ismas the architecture (target) in menuconfig is called "Ralink RT288x/RT3xxx", under which you find a subtarget "MT7688 based boards" and finally the Omega2 profiles.
Before starting to dig through Linux sources for these SoCs I hadn't realized how difficult it is to relate chip names to their architectures and drivers. There's little logic in it, but a lot of history.
How would one be able to guess the MediaTek 7688 goes under the "Ralink" architecture? Of course, once you know that Ralink was once a company that made MIPS based SoCs, and was aquired by MediaTek in 2011, it makes sense.
Still, support for the MT7688 can go by any names with "ralink", "rt", "mt76" "7621" and probably quite a few others. Comments in drivers often refer to subsystems that probably once were separate chips and thus had a completely different number. And all this being in the mostly proprietary SoC world (few proper datasheets) makes it hard to figure out what belongs where. So it took a while for a beginner like me to even start connecting dots... ;-)
@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.