Got it! I just had to get my directories and paths right. I was rushing a bit, and things were not lined up exactly correctly. I think it builds for the entire project because the recursive make found my package on its own, but I wasn't specifying it exactly right when I tried to build it individually.
@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.
@George-Gerber, it is there, you may miss it because it falls under 0.1.10 i.e. omega2p-v0.1.10-b160.bin
@Sergiy-Tarasov, I have had some success using what is most likely a hack and not recommended.
Uncomment line 1 "reboot_core" in the file /etc/opkg/distfeeds.conf
opkg --force-depends install kmod-i2c-gpio-custom
Now the hack, because it was for a higher kenel version the libraries are installed to /lib/module/<kenel-version> so we need to copy them across to the current version, in my case:
cp /lib/modules/4.4.131/* /lib/4.47/
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... ;-)