On Tue, 2011-10-11 at 11:49 +0800, Andy Green wrote:
On 10/11/2011 11:43 AM, Somebody in the thread at some point said:
Cool. In the absence of a official Android 3.1 common tree, I sat down today and actually did the same with the TI omapzoom p-common tree (just adding the linaro+android defconfigs and base origen support).
Is there any reason not to base off my version of it? There's no guarantee TI's tree will go on for any longer than they have a use for it whereas I am planning to do this for a whole cycle.
No specific reason not to, just that from reading your announcement from last week, I thought the p-android-3.1 branch was just the rebased android common tree, and it wasn't clear if the tilt tree had other things in it or not.
There were a few usb related mis-merges in that tree that wouldn't compile, so I fixed up. I'm guessing you've already hit and fixed them as well, but if not, you can just grab it, its here:
My tree has worked for a while.
git://git.linaro.org/people/jstultz/android.git linaro-android-3.1-fport
There's only one new change in Nico's tree that I didn't get to test earlier today, but earlier I got it booting on both pandas, beagle, and origen.
That is good.
While we're talking, I noticed cpufreq topic on the re-ordered tree looks like it's a selfcontained little history for a new governor called 'interactive'. Do you know anything about the history of efforts to get this upstream?
So its never been submitted that I'm aware of. I've chatted with some non-android google folks who do more upstream cpufreq work, and they weren't really aware of it.
It was on my list for the trivial-tree earlier, but I never got to it (I still need to get the smaller cgroup patches sent out). If you think its more interesting, I can bump its priority and try to get it out for discussion. I have neglected the trivial tree work this cycle, so it would probably be good to get another item or two our for discussion.
thanks -john