Well, at the moment I'm stuck.
I got the Moto kernel code but I don't know what options I need to turn on to build it. That's not obvious at all. I tried pulling the stock 2.2 Froyo kernel and it blows up immediately on boot (I can get a logcat out of it though - the kernel itself starts, but the rest of the OS does not) and the same thing happens with the overclock version that's flying around here.
As near as I can determine the audio problem is in the kernel and may be as simple as a library mismatch with the zImage file. With the Motorola source it should be a piece of cake to drop it in the correct place in the Android build tree and compile it up, if I knew where it went - but I don't - and if I had a config file - and I don't. Alternatively, if I knew the correct set of options that's just as good, but none of the processor options match what a "dmesg" displays. There are some that are close, but no exact matches. That sucks.
Never mind the rest of the driver set.
I'm going to keep screwing with it, but someone has to know because there's a running kernel in the build. It just looks like it's configured incorrectly or a library problem and thus won't work with the other devices.
Oh, there's more possibly-bad news. I tried to enable the wifi tethering on CM7 through the system settings extension and got errors in the logcat that didn't make a lot of sense. That may be something stupid (e.g. yet another library problem) but if its not there's another possibility that nobody's going to like - it may be that the chipset in question can't go into infrastructure mode, which means no hotspot, CM7 or no.
I'm also trying to chase down the MMS abortion that Virgin uses. That shouldn't be too tough but github appears to be hosed (again!) and the repository of another guy who has a CM7 implementation on the Optimus (which should have the same MMS issue and thus be able to be cribbed for a fix) won't transfer.
So.... for right now I'm blocked on everything I want to try to accomplish. Without the drivers being correctly set up in the kernel none of the hardware is going to work. The kernel ITSELF appears to find the devices however, which implies that when it was grafted in it did NOT include the loadables that came with it - that's easily fixed once I know where the kernel came from, and once fixed it may literally fix basically everything on the hardware side.
Waiting to hear back from Isaac and also investigating other options; if anyone can track that kernel down from the ID string in the system it would help a LOT, as somewhere there should be a package containing the kernel itself and *also* a handful of auxiliary files.
Until I manage movement on one of the above there's not much I can do.
Oh, the VM activation APK appears to run but doesn't work, although I'll try that again once we get a bit further along. I was hoping we could provision directly on CM7, but that looks to not be in the cards.
Oh, here's another good one - the motorola code they released doesn't compile. Off to see if Github is fixed enough to grab something that hopefully will build and run (!)
As far as the Wifi Tethering goes, I know the HTC Thunderbolt sports the exact same chipset as the Triumph and it can tether under infrastructure mode. But, that to me is the last thing we should worry about seeing as the audio and other things don't work.
Dog pictures are cute but completely off topic.
So everything works, exept audio, correct? I am curious about HDMI out, does this still work in Cyanogenmod 7? has it been tested? Bluetooth is never used by me, so if this is fixed, I could begin my testing, if needed.