[HTC Amaze 4G] ericdjobs:
Yeah.. I would say more that I dove right in because I learn best hands on.. you know break 1,000 things then have to fix it all up haha.

I have not given up :) I just haven't made anything I have felt like I could release. I think there's some kind of size limit to the kernel, actually, because I';ve literally had to reset with a stock RUU (Maybe it jacks up partition tables? not sure) at least 50 times now... Anything over 3.8-4meg (the zImage, that is.) seems to brick. I've had a couple working builds, though... but always crazy bugs that I have yet to work out. But then again I've been trying some pretty insane stuff!

I think what I'm going to try and do is take a well known kernel like Sultan's or TeamHydra's very popular sensation kernel and just merge in the ruby changes, so we get a very well updated (all around) kernel with tons of enhancements, then ideally I want to build it with the cortex-a8 optimized linaro 4.7 toolchain as well as all the cortex-a9 enhancement flags and -O3 and strict aliasing and other such enhancements... the problem with -O3 and strict aliasing is that even small errors halt the entire build, which would be considered warnings otherwise... then it's a long long process of drudging through code

I treat it more as a massive learning experience for myself but hopefully I can produce something viable. Also just started to attempt a Linaro build of CM10.1 (nightly) with Bionic (the new glibc replacement)... but work has kept me pretty busy lately so it has been a couple days since I've just dedicated hours to tinkering. This is entirely new territory for me so it's still lots and lots and lots of learning and lots of trial and error. But it's really a lot of fun, honestly, haha. There's nothing more satisfying than banging your head against a compile for 6+ hours fixing error after error after error to see it finally finish (then realize your kernel image is too big, then have to remove some features... then that causes another boatload of errors... ugh)

Speaking of which cowboy, there's a pretty decent Sense kernel that sultan maintains for the Sensation (Which is incredibly similar to our device, sans the TI WiLink chip in ours for BT/Wifi/GPS/FM).. it's basically just a matter of updating board-ruby.c and the related board-ruby files to be in-line and then you simply start with the default ruby config (make ruby_defconfig) and then use menu config (or just edit .config) from there to add/remove features etc. But for wireless to work it seems that compat-wireless MUST be used.. I don't understand it because the wl12xx drivers are actually part of the mainline linux kernel now but HTC did some weird crap... i actually tried a full revamp of the wireless subsystem updating the wl12xx drivers to the latest possible as well as the firmware (as well as some hacked firmware with full working monitor mode!) but it just flat out refuses to work... this could easily be attributed to my n00b status, though... but when I build the older drivers using compat-wireless wifi works fine.. so who knows.

Have to remember that Sports is shooting for CM10.1 support so kernel wise he can only do so much in that regard. Our best bet honestly seems to be with a well maintained msm8660 kernel for a different device then just updating it for the ruby and then building the kernel modules with compat-wireless.

Also I can't seem to figure out why I can't get USB OTG to work... Maybe the hardware in the Ruby simply doesn't support outputting power as to power the USB device? ALl the support is there, and it even seems like (there's code for it, in the board-ruby.c file) there's support for power output to make it work.. but it simply does not work. I don't have an Accessory Charging Adapter to see if it's the OTG support or a power-supply problem (The MicroUSB port on the device has to supply power to power any USB accessories/flash drives, or you use an ACA to provide power) I believe it IS functioning though, because there's a sysfs interface for port type and how it's currently functioning and when I plug in a usbOTG adapter the port most-definitely goes into Host Mode.. so I'm pretty sure it's just a matter of power output.. and I don't have any idea why it's not working.