On 29 January 2013 10:09, Viresh Kumar wrote:
> With the addition of following patch, related_cpus is required to be set by
> cpufreq platform drivers:
>
> commit c1070fd743533efb54e98142252283583f379190
> Author: Viresh Kumar
> Date: Mon Jan 14 13:23:04 2013 +
>
> cpufreq: Simplify cpu
With the addition of following patch, related_cpus is required to be set by
cpufreq platform drivers:
commit c1070fd743533efb54e98142252283583f379190
Author: Viresh Kumar
Date: Mon Jan 14 13:23:04 2013 +
cpufreq: Simplify cpufreq_add_dev()
Because this change is required by all platfo
This reverts commit 956f33948b95aa91f6cbc6860087671c6ac1de4b.
With the addition of following patch, this change/variable is not required:
commit b9ba2725343ae57add3f324dfa5074167f48de96
Author: Viresh Kumar
Date: Mon Jan 14 13:23:03 2013 +
cpufreq: Simplify __cpufreq_remove_dev()
Sig
On 28 January 2013 14:17, Andy Green wrote:
> No, "blowing chunks" (slang for vomiting) is different than "blowing
> up"... the 4460 has a separate comparator that is able to reset the SoC if
> it gets really too hot.
>
Ah, another term for my collection of disgusting things to talk about
during
Hi, All
Android team now has tools for updating the kernel related files without
recreating the sdcard.
The detail information about the tools is described here:
https://wiki.linaro.org/Platform/Android/KernelUpdateTools
And here just list some examples:
1. update all the kernel related files wit
On 28/01/13 21:10, the mail apparently from Renato Golin included:
On 28 January 2013 12:43, Andy Green mailto:andy.gr...@linaro.org>> wrote:
Without this or something doing a similar deal, a Panda ES will blow
chunks after a short period at 1.2GHz.
Hi Andy,
I agree kernel panic is be
On 28 January 2013 12:43, Andy Green wrote:
> Without this or something doing a similar deal, a Panda ES will blow
> chunks after a short period at 1.2GHz.
Hi Andy,
I agree kernel panic is better than blowing up the board, but that might
indicate the scaling is not working very well.
Also, do
On 26/01/13 06:06, the mail apparently from Renato Golin included:
Hi folks,
I'm testing different kernels with the LLVM LAVA job and the latest one
segfaulted. If you search for the phrase on the subject on the URL below:
https://validation.linaro.org/lava-server/scheduler/job/46067/log_file
On 28 January 2013 18:16, Amit Kucheria wrote:
> On Mon, Jan 28, 2013 at 11:38 AM, Hongbo Zhang
> wrote:
>> This script aims at testing all the trip points are crossed or not, since the
>> trip points are usually very high and can be reached only in extreme
>> conditions
>> like high environmen
On Mon, Jan 28, 2013 at 11:38 AM, Hongbo Zhang wrote:
> This script aims at testing all the trip points are crossed or not, since the
> trip points are usually very high and can be reached only in extreme
> conditions
> like high environment temerature etc, in normal conditions they cannot be all
On 27 January 2013 23:30, Michael Hudson-Doyle wrote:
> In the past hasn't this sort of problem usually turned out to be heat
> related? Or is this something else?
>
Hi Michael,
It could very well be, I don't know how the heating problem used to
manifest before...
However, the original kernel
11 matches
Mail list logo