I used to access Linaro gitweb below all the time. But from
yesterday, I found it stops working for me. Anyone else experienced
the same problem, or it's just the problem on my end?
http://git.linaro.org/gitweb
--
Regards,
Shawn
Some of Linaro developers works with ARM devices older then ARMv7-a
architecture. Other people experiments with hard-float ABI. Each of them has
to rebuild toolchain for own use and that means playing with components to
have them build properly.
But it is no more - I made some patches and armel-cross-toolchain-base since
1.53 version + newer source packages for gcc-4.[45]-armel-cross have support
for "debian/flavour" file which allows to set some flags related to toolchain
build.
So far supported things are:
- ARM architecture
- float ABI
- FPU mode
- Thumb mode
This feature is not merged into regular Ubuntu packages yet as this is work in
progress which needs to be cleaned first.
http://people.linaro.org/~hrw/armel-cross-toolchain/ has all source packages
needed.
Regards,
--
JID: hrw(a)jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
One of the Valgrind subtools is Cachegrind; this is a cache
profiler. (It simulates the I1, D1 and L2 caches so it can
pinpoint the sources of cache misses in application code.)
On x86 Cachegrind automatically queries the host CPU to find out
what sort/size of cache it has installed, and by default will
simulate that sort of cache. (You can also use command line
options to specify a different cache layout to model.)
On ARM, the ARMv7 VMSA coprocessor registers which describe the
cache geometry are privileged-mode access only. This means
cachegrind can't do the same "default cache model is the same as
your real CPU" behaviour that it does on x86.
Can the kernel folks on this list suggest whether it would be a
reasonable idea for the kernel to provide some sort of userspace
API so tools like cachegrind can find out the cache geometry?
Thanks in advance
-- PMM
Some of Linaro developers works with ARM devices older then ARMv7-a
architecture. Other people experiments with hard-float ABI. Each of them has
to rebuild toolchain for own use and that means playing with components to
have them build properly.
But it is no more - I made some patches and armel-cross-toolchain-base since
1.53 version + newer source packages for gcc-4.[45]-armel-cross have support
for "debian/flavour" file which allows to set some flags related to toolchain
build.
So far supported things are:
- ARM architecture
- float ABI
- FPU mode
- Thumb mode
This feature is not merged into regular Ubuntu packages yet as this is work in
progress which needs to be cleaned first.
http://people.linaro.org/~hrw/armel-cross-toolchain/ has all source packages
needed.
Regards,
--
JID: hrw(a)jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
Vishwa,
I have a more-or-less complete set of example code for CPU context save/restore, currently supporting A5/A8/A9 and with planned support for Eagle.
It is structured as "firmware" at the moment, but it would be much better if it was integrated into the ARM Linux kernel. The idea is the kernel calls it from CPUidle, and it saves all CPU context and cuts the power. Then when power returns, it restores all CPU context and returns to the kernel as if nothing has happened.
It handles just the CPU and cluster context, which on A9mpcore includes MMU, GIC, VFP, SCU, L2cc, Debug, etc. It takes care of cleaning caches and entering/leaving the coherency domain. There is also support for TrustZone, but as you say that's quite platform-specific.
So we would need to integrate this with the SoC-specific code somehow.
Jon.
--
I work Tue/Wed/Fri only
Jon Callan, Staff Software Engineer, Processor Division
ARM Cambridge / +44 1223 400814
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.