I'm having a hard time keeping track of the names people are calling this kernel.. so in light of various others naming their kernels.. i shall call this one.. hmmm. i suck at naming things.. the first thing that popped into my head was...
Razzle Dazzle <--kidding. just an example of why I stick to appending dates on the filenames.. (and i will do the same for my children)
http://home.comcast.net/~ibladesi/TF...omVchanges.zip <---This boots at 1232mhz, and insults your manhood.
and for those menly men that like their tf101 fast all the time. 1592mhz boot clock..
These two have very high vcore... it is meant for people who would like to adjust their voltage themselves. If you have trouble with the normal kernels, and suspect the undervolting is causing the issues... try this.. but remember to undervolt.. really...
Newer stuff is in bold... just in case you can't read dates.
Testing out memory timings that may bite you.. If anyone can help cut through the bullshit that is MC/EMC clocks... just chime in here.. Originally I increased (slowed down) the timings and bumped up the clock by 33mhz.. and got fail. So... advancing the timings it is.. They are pretty pitiful stock.. What really pisses me off is the missing 33mhz (and thus 66mhz from emc).. we could use that... Well.. lets see if waking up the wimpy timings helps.
edit:1680mhz. The updater-script still says the max is 1656mhz for this zip.. but the max is 1680.. i promise
Same as above, but a slightly advance of the memory timings. Am I even using the correct word, I seem to be in car tuning mode.. Tighter memory timings, I guess? My plan is to push it until its crashy. This is not crashy: http://home.comcast.net/~ibladesi/TF101-08-24-2011.zip
edit: throttle_temp is at 56... voltage bumped up for freqs above 1224.. So this could get a little toasty
Edit: Now on github. http://www.github.com/ibladesi
Also because some people asked..