On Mon, 2012-07-23 at 10:25 +0200, Alexander Sack wrote:

what platform is armlt-staging-alt-open targeting compared to armlt-tracking-open?

It's for TC2. This build has scheduler features enabled for big.LITTLE, and it includes power management (PM) code, i.e. cpuidle and cpufreq, which is available on TC2, but not other CoreTies.

Unfortuately, the PM code interacted with the Android kernel in an undesirable way that we didn't manage to get to the bottom of in time for this release, so it is disabled in the build.

On Mon, 2012-07-23 at 10:56 +0200, Alexander Sack wrote:

On Mon, Jul 23, 2012 at 10:44 AM, Jon Medhurst (Tixy) tixy@linaro.org wrote:

...

On Mon, 2012-07-23 at 10:25 +0200, Alexander Sack wrote:

...

what platform is armlt-staging-alt-open targeting compared to armlt-tracking-open?

It's for TC2. This build has scheduler features enabled for big.LITTLE, and it includes power management (PM) code, i.e. cpuidle and cpufreq, which is available on TC2, but not other CoreTies.

IC. That's what I remembered. Why is it staging vs. tracking though? Is the TC2 code against an old/stable (vs. tip) kernel?

No, TC2 is on latest kernel.

It was called staging because we already had tracking for the normal release, and I resurrected the old staging builds (which were used before we had the 'common' tree). We needed this because we were in such a rush to meet the release deadline, we didn't have time to base the code of linux-linaro.