Hi,
I've tried to use Linaro 11.08 nano image with vexpress 11.08 hwpack
but the board hangs in the init script and I never get the shell
prompt.
if I use the linaro 11.07 nano image with the 11.08 hwpack, the
vexpress board boot successfully. Did someone else face the same
problem ?
Regards,
Vincent
Hi,
I've put together LTTng 2.0 tools into overlay PPA to use and evaluate
it on ARM platforms.
LTTng 2.0 [1] is a tracer toolchain that allows integrated kernel and
user-space tracing from a single user interface: the "lttng" command.
LTTng 2.0 kernel tracer modules build against a vanilla or distribution
kernel, without need for additional patches. It is currently in
pre-release state to gather feedback from users.
I've taken the packages from LTTng Daily Builds PPA [2], modified it to
build and run on armel and pushed it to overlay.
To install it:
$ sudo apt-add-repository ppa:linaro-maintainers/overlay
$ sudo apt-get update
$ sudo apt-get install lttng-tools lttng-modules-dkms babeltrace
To run it, we need to create a session
$ sudo lttng create mysession
To list the available kernel events:
$ sudo lttng list -k
Enable all/some events for this session
$ sudo lttng enable-event -a -k
Start the tracing:
$ sudo lttng start
By default traces are saved in ~/lttng-traces/mysession-<date>-<time>/
When you're done:
$ sudo lttng stop
You can then read the trace with babeltrace:
$ babeltrace /path/to/trace/dir
Please test it and give feedback.
Regards,
Avik
[1] http://lttng.org/lttng2.0
[2] https://launchpad.net/~lttng/+archive/daily
Hi -
TI Landing Team has added a couple of new trees to our git repo over the
weekend
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git;a=summary
Both of them track Linus HEAD, currently at 3.1-rc8.
First is "linaro-androidization-tracking", this is Linus HEAD plus a set
of Androidization patches formed from common-3.0 and common-3.1.
"common-3.1 you say?", yes, TI needed a tracking Androidization tree and
have made their own public one using pieces from common-3.1.
You can find TI's tree that was an ingredient in this here if you're
interested, it's public
http://git.omapzoom.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/p-androi…
Due to android.git.kernel.org down, AFAIK there's no public access to
common-3.1 direct otherwise at the moment.
So what's this tree good for? If you have a kernel for any arch or
board that is based on Linus HEAD, 3.1-rc8 at the moment, you can merge
or rebase a copy of it with linaro-androidization-tracking to create an
Android version of the same kernel.
That's very handy if you did your work to get stuff looking good on
Vanilla Linus HEAD and don't want to repeat the effort to get the same
features coming in an Android kernel.
Until now there was no way to casually Androidize a Linus HEAD basis
tree unless it happened common-3.x was tracking it, which it only does
for a short period at the end. It meant that you had to use old release
to start integrating and adding drivers for Android and backport from
HEAD anything nice that was coming. Now with this tree, you can do your
work on Linus HEAD and fork off working release trees when Linus HEAD
goes through a release.
This Androidization tree is generic and should be usable for any arch or
board, there's nothing TI specific in there. Why then is TI Landing
team announcing it / TI go to the effort of creating their original one
we based off? Nobody else in Linaro wanted to do the work to create and
maintain it, so we own it at the moment. We'll have to see how tough it
is to keep tracking Linus HEAD through the post-release patchstorm but
reviewing the Androidization patchset I'm cautiously optimistic.
I don't have any connection to Google guys who are basically doing the
same work on common-3.x, but it would be very cool to be able to
cooperate with them on bringing this Androidization patchset forward for
everyone's benefit.
The second branch is "tilt-android-tracking". This is our main tracking
branch tilt-tracking for Panda enablement we have been running for some
months combined with "linaro-androidization-tracking" above.
This gets you an effective Panda enabled "3.1 preview" kernel that we
have had for a while on Vanilla also on Android in an ongoing way.
Current status of it is
+ 1080p SGX acceleration
- Suspend borked
- WLAN borked
But we only generated it Sunday, we are working on those issues now.
Lastly TILT is also providing tracking versions of the Android autobuilt
Panda-LEB tarballs that are ready to use. These are the Autobuilt
tarballs with the kernel replaced with a tracking one by us. You can
find them linked from our git repo in tilt-android-tracking column of
the status table there.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
While compiling with s3c2410_defconfig, we receive 4 section mismatch
warnings.
Patch 1 addresses a couple of warnings related to usb_simtec_init().
Patch 2 addresses mismatch warnings in a couple of mach-*/irq.c files.
Changes for V2:
* The original patch is splitted to address to different logical
solutions.
* __initdata attribute is removed from struct sysdev_driver
structures and __init attribute is removed from all referenced
function definitions.
The patches are rebased on v3.1-rc8. They are only build tested,
they are not boot tested on any hardware.
Tushar Behera (2):
ARM: S3C2410: Add __init attribute to usb_simtec_init()
ARM: S3C2410: irq: Remove __init attributes to fix compilation
warning
arch/arm/mach-s3c2410/usb-simtec.c | 2 +-
arch/arm/mach-s3c2410/usb-simtec.h | 2 +-
arch/arm/mach-s3c2416/irq.c | 4 ++--
arch/arm/mach-s3c2443/irq.c | 4 ++--
4 files changed, 6 insertions(+), 6 deletions(-)
--
1.7.4.1
The following changes since commit 212bd07b46a8928a05b0dd0062a5c967a784d122:
Revert "armv7: adapt omap3 to the new cache maintenance framework"
(2011-09-28 23:53:14 -0600)
are available in the git repository at:
git://git.linaro.org/bsp/freescale/u-boot-linaro.git master
Eric Miao (2):
mxc_i2c: fix i2c_probe() failure by using i2c_reset()
mx53loco: add support for MC34708
board/freescale/mx53loco/mx53loco.c | 57 +++++++++++++++++++++++++++--------
drivers/i2c/mxc_i2c.c | 3 +-
include/configs/mx53loco.h | 3 +-
3 files changed, 47 insertions(+), 16 deletions(-)
The two patches below added support for the new i.MX53 QuickStart
boards, which are based on Freescale's own MC34708 PMIC (Power
Management IC), replacing the previous Dialog Semi's DA9053.
The resulting binary will be working on both the DA9053 based
boards and the newly MC34708 based boards.
[PATCH 1/2] mxc_i2c: fix i2c_probe() failure by using i2c_reset()
[PATCH 2/2] mx53loco: add support for MC34708
Hi all, does anyone know why all the hwpack builds have started failing?
See, for example:
http://snapshots.linaro.org/11.05-daily/linaro-hwpacks/panda/20111006/0/bui…
...a similar problem seems to have affected the recent builds for every hwpack.
Looks like some build-depends package is not getting installed properly.
Cheers
---Dave
I know this has come up before, but I'd like to raise it again: Is there any
reason for the lack of consistency between directory layouts for:
http://snapshots.linaro.org/oneiric/
vs.
http://snapshots.linaro.org/11.05-daily/
Would it be possible to rename the oneiric directory to 11.11-daily and
split the hwpacks off into a linaro-hwpacks directory like the 11.04 images?
Also, keeping some kind of -oneiric or -11.11 on the image/hwpack dirs
probably makes sense, but are we planning on changing anything after these
become the default LEB images?
Thanks,
Paul Larson
