Okay now I can compile the firmware with the Codec for SGTL5000 I'm hanging again.
The kernel module is loaded but a cat /proc/asound/cards lists still --- so soundcards --- I'm not really sure but I think I just have a codec installed but no "card". Am I right if I think I need a card driver in build_dir/target-mipsel_24kc_musl/linux-ramips_mt7688/linux-4.4.52/sound/soc/mediatek which 'uses' the codec?
Does anyone know how to get this thing up and running? It's so exhausting...
@Luciano-S @WereCatf told here that the devs of the Omega2 forgot to enable CONFIG_DEVMEM in the newer firmware. The last working one is 0.1.6 b137
So my guess is that it is fixed in the next release if it is indeed just a forgotten flag.
@Luciano-S. Yea,. And what is funny is I got a Windows 10, 8" tablet (Signature Edition) for $50, which upgraded to Win 10 Anniversary edition with no issues, so I could work with and monitor my Omegas. I did go back and spend $25 for a BT keyboard/mouse combo. Everyone wants a tiny computer, but all these things out there from LattePanda to the ones in that video all require a bunch of dongles and cords to connect and run. The tablet is not the fastest, nor does it have the biggest storage, but it works for interfacing with the Omegas. Hell, I can use my iPad to SSH into the Omegas (also using a BT keyboard for sanity) and it works just fine.
Some of these single board computers end up needing so many things to get them working, that it just isn't worth it. Especially when they say these are "consumption devices" or set-top boxes. There are far better devices, and if you wanna put a Raspberry pi in a case with an LCD screen, it is probably cheaper overall to get a cheap tablet and swap out the OS.
I get it, people want to hack their own stuff because they can. As cool as the ideas can be, the market is getting flooded with these tiny computers.
I use Zabbix for a lot of management purposes, and it has a discovery mode that you can customize. I used discovery in a large ISP environment to scan for new customer nodes coming online, scan the nodes for correct configuration, send alerts to techs when incorrectly configured systems or rogues were found, etc... The quality of the ISP's network went way up when we started detecting configuration issues BEFORE they caused problems.
The only downside is this is a rather application-specific service, so you have a challenge to make it application neutral. that probably means covering the basic common system settings, and making a API that is easy to integrate into the user's application. Being that these devices are great for swarm applications, your idea has a lot of merit. What would be better than a self-configuring swarm?
But I ageree this should be a generic Linux app, just keep it light weight so it works as well on small systems as large ones.
There are a lot of tools to look at that solve needs like this out there, in configuration management and system monitoring, so get some exposure to what others have done, might give you some good ideas.