Hi,
the toolchain WG is officially releasing a 4.7 based compiler this
month - and I'd like it to become the default, let's stay ahead of the
line.
We know the userland is fine since we have working iMX6 and Panda
builds done with 4.7.
I've created gcc47 builds for every board (simply replace gcc46 with
gcc47 in the name).
The following builds failed in the initial run:
~linaro-android/imx53-ics-gcc47-freescalelt-stable-open
~linaro-android/snowball-ics-gcc47-igloo-tracking-blob
~linaro-android/vexpress-ics-gcc47-armlt-stable-open
~linaro-android/panda-ics-gcc47-kwg-upstream-open
~linaro-android/panda-ics-gcc47-omapzoom-stable-blob
~linaro-android/panda-ics-gcc47-tilt-stable-blob
~linaro-android/origen-ics-gcc47-samsunglt-tracking-blob
Most of the failures look like random linaro-build breakage
("hudson.util.IOException2: remote file operation failed:
/mnt/jenkins/workspace/linaro-android_imx53-ics-gcc47-freescalelt-stable-open
at hudson.remoting.Channel@1150f8c:i-2468d843"), so we're actually
better than it looks. ;)
I'm restarting the failed builds - hopefully we'll have some more
working builds in the evening and useful error messages for the ones
that keep failing (there were a couple of initial failures (fixed by
now) in the iMX6 and Origen kernels - expecting to see some more of
those, but they should be easily fixable.
ttyl
bero
During ELC a few people asked me if Linaro had something bigger than
nano and smaller than Ubuntu that they could use to build stuff. Of
course I said Android, but a lot of people actually want a regular
Linux platform where they can easily recompile what they need to hack
on, add their own libs and scripts and generally work in an "embedded,
cross build way." I know there's OpenEmbedded and I've heard of
something called "livebuild." Does anyone have anymore info? This
class of users is arguably the largest class of people using these
boards so creating something targeted at them would allow them to get
all the benefits of Linaro in a easy to use fashion.
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Friends of the greed robot,
The attached file is used to compile the MM libs from one of our vendor.
On line 224 the variable TARGET_CROSS_COMPILE is assigned the value
'arm-eabi-', forcing the build script to look in $PATH for the compiler.
This is obviously not what we want.
I commented out 218 and added 219 and the libs are now compiled with
'arm-linux-androideabi-'.
I would like to know if there is a better way to fetch the
linaro-android toolchain or if it is ok to simply reference
TARGET_TOOL_PREFIX the way I did.
Regards,
Mathieu.
Hi List,
You may be able to answer this question on Ask Linaro:
http://ask.linaro.org/questions/1063/can-someone-help-with-linker-error-on-…
The guy is getting compile warnings:
arm-eabi-ld: warning: unwinding may not work because EXIDX input section
8 of arch/arm/nwfpe/built-in.o is not in EXIDX output section
And his kernel doesn't seem to boot (though it could be a mistake on the
user's side).
Cheers,
Michael.
--
Michael Opdenacker - Community tech support
Linaro, http://linaro.org
Phone: +33 484 253 396
IRC: 'opm' in #linaro on irc.freenode.net
Hi All,
I have made a Hack for Download Manger in Android:
The the bug report is here for reference:
https://bugs.launchpad.net/linaro-android/+bug/919775
The hack is here for reference:
http://review.android.git.linaro.org/#change,1833
Kindly let me know if you are facing issues with Download Manager, and this
is a common prevailing problem across?
Are there any standard method, patches by which you are able to overcome
this issue.
I have tried enabling IPV6 and netfilter in kernel for Linaro Origen with
no help.
So, had to resort to the Android hack mentioned above
PS: Any comments are welcome!
With Regards,
Annamalai
On 9 April 2012 06:01, Kejun Zhou <kejun.zhou(a)linaro.org> wrote:
> Hi Rob,
> Would you tell me the CPUIDLE test steps in pm-qa?
>
> As the pm-qa needs to run in bash, and use the "make" tool, but the Android
> only has its own shell, the "make" tool is not available in Android system.
Why is pm-qa running make? Is it just to load the system?
>
> Thank a lot.
>
>
> Hi Zach,
> The limitation of Android system(bash and make) blocks the CPUIDLE too much.
Kejun, if make is just being used to make the system busy, we have
other tools for that. Talk to Amit about some of the commands he
integrated for big.LITTLE testing.
>
>
> BRs,
> Kejun
>
>
>
> On 7 April 2012 03:18, Andrey Konovalov <andrey.konovalov(a)linaro.org> wrote:
>>
>> Hi Kejun,
>>
>> Regarding your two questions below:
>> 1. Guess the questions on CPUIDLE implementation will be much better
>> answered by Rob Lee (Cc-ed).
>> 2. The PM WG has tests for their features:
>>
>> https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/QA/Scripts#Cpuidle
>>
>> https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/QA/Scripts#Pre-re…
>>
>> Thanks,
>> Andrey
>>
>>
>> On 04/06/2012 01:29 PM, Kejun Zhou wrote:
>>>
>>> Hi Andrey,
>>>
>>> I am Kejun from Linaro Android team. I got a task to integrate the
>>> CPUIDLE to Linaro Android kernel branch from Zach.
>>>
>>> I found the CPUIDLE is included in linux-linaro-3.3-2012.03-2 from your
>>> email, and merged Snowball CPUIDLE to linaro-android-12.03-release
>>> kernel.
>>>
>>>
>>> I have some questions about how to verify whether this CPUIDLE feature
>>> is integrated or not.
>>>
>>> 1. I found that the cpu_do_idle() is executed. But the code in "if () "
>>> won't be executed after Android starting up. And the current is between
>>> 380mA ~ 490mA, I thinks when CPUIDLE is working, the current should be
>>> more low than 380mA.
>>>
>>> static inline int ux500_enter_idle(struct cpuidle_device *dev,
>>> struct cpuidle_driver *drv, int index)
>>> {
>>>
>>> ..
>>> if (atomic_inc_return(&master) == num_online_cpus()) {
>>>
>>> ..
>>> }
>>>
>>> wfi:
>>> cpu_do_idle()
>>>
>>> ...
>>> }
>>>
>>>
>>> 2. Is there some method to test the CPUIDLE feature from the Linux
>>> console?
>>>
>>> Thanks a lot.
>>>
>>> BRs,
>>> Kejun.
>>>
>>>
>>> On 28 March 2012 04:11, Andrey Konovalov <andrey.konovalov(a)linaro.org
>>> <mailto:andrey.konovalov@linaro.org>> wrote:
>>>
>>> Greetings,
>>>
>>> The Linaro Kernel Working Group (KWG) and the Linaro Platform
>>> Group are excited to announce the availability our March 2012
>>> development snapshot:
>>>
>>> linux-linaro-3.3-2012.03-2
>>>
>>> As the word "snapshot" implies, these are meant as development kernels
>>> and have not been fully validated. You should expect issues and to
>>> help
>>> us deliver a better kernel in the future, please file bugs in
>>> Launchpad at
>>> https://bugs.launchpad.net/__linux-linaro
>>> <https://bugs.launchpad.net/linux-linaro>.
>>>
>>>
>>> The source tarball is available at:
>>>
>>>
>>> https://launchpad.net/linux-__linaro/devtrack/12.03/+__download/linux-linar…
>>>
>>>
>>> <https://launchpad.net/linux-linaro/devtrack/12.03/+download/linux-linaro-3.…>
>>>
>>> The kernel sources can also be accessed using git at:
>>> git://git.linaro.org/kernel/__linux-linaro-tracking.git
>>> <http://git.linaro.org/kernel/linux-linaro-tracking.git>
>>>
>>> tag: linux-linaro-3.3-2012.03-2
>>>
>>> This kernel includes the following changes from the 2012.02 kernel:
>>>
>>> - Update to 3.3
>>>
>>> - Various patches from Linaro
>>> * Versatile Express patches from ARM LT
>>> * Gator module for ARM's Streamline Performance Ananlyzer from ARM
>>> LT
>>> * updated irq_domain patch set from Grant L.
>>> * cpuidle core consolidation, cpuidle support for i.MX5/6 and ST-E
>>> u8500 from PM WG
>>> * updated patch set support for common save and restore code to the
>>> Samsung exynos platform from PM WG
>>> * updated thermal_cpu_cooling patch set from the power management WG
>>> * UFS patches from kernel WG
>>> * eMMC4.5 patches from kernel WG
>>> * initial dma-buf patch set and some related components for UMM
>>>
>>> - AOSP 3.3 android patch set
>>>
>>> A full change log against the 3.3 release is available at:
>>> https://launchpad.net/linux-__linaro/devtrack/12.03
>>>
>>> <https://launchpad.net/linux-linaro/devtrack/12.03>
>>>
>>> High Priority Known Issues:
>>>
>>> - ANDROID_RAM_CONSOLE must be disabled for the android kernel to boot.
>>>
>>> _________________________________________________
>>> linaro-dev mailing list
>>> linaro-dev(a)lists.linaro.org <mailto:linaro-dev@lists.linaro.org>
>>> http://lists.linaro.org/__mailman/listinfo/linaro-dev
>>> <http://lists.linaro.org/mailman/listinfo/linaro-dev>
>>>
>>>
>>
>
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Yeah, that should be okay. Though we could do it using a separate
branch. That may make ongoing maintenance easier. We can name the
branch:
linaro_android_4.0.4_origen
Will that work?
On 9 April 2012 07:20, Annamalai Lakshmanan
<annamalai.lakshmanan(a)linaro.org> wrote:
> Hi Zach,
>
> I would like to create a branch in /device/linaro/origen/.git:
> This will enable me push changes for 3.3 kernel and track it seperately.
> 3.3 is still not very matures so it currently requires changes like
> disabling HW rendering , etc..
>
> Would it be acceptable for you, if so please let me know since branch
> creation would require admin right.
>
> With Regards,
> Annamalai
>
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog