Hello everyone,
In the spirit of reaching out to the Linaro community, I'd like to
engage in some conversation with those working on the HardFP ABI switch
and toolchain effort, since we will shortly be doing the same in the
Fedora ARM community. The intention is to support hardfp in time for the
Fedora 15 ARM release, which *will* lag behind the x86 F-15 release.
Anyway. I could do with some pointers to the current state of things,
and who I should talk to and engage with at the LDS in another week. I
will be there representing the Fedora ARM community. And I look forward
to meeting those of you who don't already know me from other lives ;)
Jon.
I tried out:
git://git.secretlab.ca/git/linux-2.6.git devicetree/test
plus the following commits from jk's dtbimage branch:
4c2eddb89542f73fe626813e3cdafc789f931aec
arm: dtbImage support
4cb80ac96489220554d28f6fde527aeef83e628b
arm/dtbimage: copy dtb blob to offset from image base
A local patch to modify the Tegra devicetree support to support
Seaboard instead of Harmony.
... on an NVIDIA Tegra Seaboard board.
This patch series includes fixes to that branch to get Tegra booting to
user-space.
Note that soon after user-space starts, the system still crashes with:
Unhandled prefetch abort: debug event (0x002) at 0x40e97714
However, this happens with or without actually providing a devicetree
image to the kernel (I modified jk's dtbimage wrapper just to jump
straight to the regular kernel startup, thus not providing a devicetree
at all). So, I suspect it's some unrelated issue. I'll try to follow up
and solve that too.
Stephen Warren (3):
ARM: Tegra: dt: Compile fix; tegra_common_init removed
ARM: Tegra: dt: Fix machine desc to match other boards.
ARM: Tegra: Move Harmony .dts file to correct place
arch/arm/boot/dts/tegra-harmony.dts | 110 +++++++++++++++++++++++++++++++-
arch/arm/mach-tegra/board-dt.c | 13 ++--
arch/arm/mach-tegra/board-harmony.dts | 113 ---------------------------------
3 files changed, 114 insertions(+), 122 deletions(-)
delete mode 100644 arch/arm/mach-tegra/board-harmony.dts
I have one 35MB tarball to share with Linaro folks. It's too big to
distribute through email. Is there any infrastructural solution for
such general file sharing purpose? (The launchpad PPA is for package
than general file sharing, and I do not want to bother.) Thanks.
--
Regards,
Shawn
Hi,
I just moved linaro-image-tools trunk to be owned by a new team, so that
it is no longer using linaro-maintainers, which wasn't really
appropriate here.
The new branch is at
https://code.launchpad.net/~linaro-image-tools/linaro-image-tools/trunk
lp:~linaro-image-tools/linaro-image-tools/trunk
Please let me know if there are any issues with this.
Thanks,
James
Hi Everybody,
If you're new to Linaro (or if you just want a refresher on how
things work in Linaro) please consider adding the Life-In-Linaro
session to your schedule:
https://blueprints.launchpad.net/linaro/+spec/linaro-other-o-life-in-linaro
This will be an introductory session that will answer some of the
questions a new Linaro Employee might have. Here are some of the
topics we will cover:
-Engineering Resources Services
-Linaro Processes
-Communicating in Linaro
-Various Technical Topics - tools, kernel, bootloader, etc.
(If you missed the Introduction to Linaro presentation at the
Dallas Sprint in January, please sign up for this session and
check "Participation Mandatory".)
See you at Linaro@UDS!
Cheers,
Matt and Andy
Hi,
The Linaro team is pleased to announce the availability of the 11.05
Beta-2 images. These are still early developer images but we encourage
all with supported hardware to use and test them by downloading from:
http://releases.linaro.org/platform/linaro-n/
Highlights of this release include:
* This milestone includes a first release of the Linaro Android
evaluation images for Beagle XM and Panda.
* Efforts from the Android team include:
* Generic AOSP builds with Linaro components.
* The Linaro Android 2.6.38 kernel.
* Toolchain packages based on Linaro toolchain release of March.
Initial benchmarks for this toolchain can be found at
https://wiki.linaro.org/JimHuang/Sandbox/LinaroToolchainAndroidBenchmarking
* An Android platform code branch for direct evaluation of the
Linaro toolchain.
* Initial low hanging fruit optimisations; integrated and upstreamed
to AOSP (16 patch sets currently).
* Mouse support for developer convenience on the Panda image.
* The 0xBenchmark package comes pre-integrated into the builds for
benchmarking and demos.
* Four images based on Ubuntu 11.04 including ubuntu-desktop, nano,
developer and ALIP.
* linaro-image-tools support for installing Android images on an SDcard
* Support for 11 different developer boards including the newly added
Freescale iMX53 LoCo board.
Using the Android-based images
=============================
The Android-based images come in three parts, system, userdata and boot.
These need to be combined to form a complete Android install. For an
explanation of how to do this please see:
https://wiki.linaro.org/Platform/Android/InstallImages
If you are interested in getting the source and building these images
yourself please see the following pages:
https://wiki.linaro.org/Platform/Android/GetSourcehttps://wiki.linaro.org/Platform/Android/BuildSource
Using the Ubuntu-based images
=============================
The Ubuntu-based images consist of two parts. A hardware pack which can
be found under the ./hwpacks directory which contains hardware specific
packages such as the kernel and bootloader. The second part is the roofs
which is combined with the hardware pack to create a complete image. For
information on how to create an image please see:
http://wiki.linaro.org/Releases/MilestoneBuilds
Comparisons
===========
A comparison of packages from the ubuntu-desktop beta and beta2 images
can be found at:
http://people.linaro.org/~jamiebennett/comparisons/comparisons-linaro-11.05…
Getting involved
================
More information on Linaro in general and the 11.05 plans can be
found at:
* Homepage: http://www.linaro.org
* Wiki: http://wiki.linaro.org
* 11.05: http://wiki.linaro.org/Releases/1105
Also subscribe to the important Linaro mailing lists and join our IRC
channels to stay on top of Linaro developments:
* Announcements:
http://lists.linaro.org/mailman/listinfo/linaro-announce
* Development:
http://lists.linaro.org/mailman/listinfo/linaro-dev
* IRC:
#linaro on irc.linaro.org or irc.freenode.net
#linaro-android irc.linaro.org or irc.freenode.net
Issues with this release
========================
For any errata issues please see:
http://wiki.linaro.org/Releases/1105/Beta2#Issues
Bug reports for this release should be filed in Launchpad against the
individual packages that are affected, if a suitable package cannot be
identified, feel free to assign them to:
http://www.launchpad.net/linaro
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
Hi,
https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/633227
seems to suggest we can now use 1GB of RAM on a Panda board.
Creating a new image using the following images and hwpacks for my Panda :
BOARD=panda linaro-media-create --rootfs ext4 --mmc /dev/mmcblk1
--binary linaro-n-developer-tar-20110426-0.tar.gz --hwpack
hwpack_linaro-panda_20110426-0_armel_supported.tar.gz --dev panda
I see that :
root@linaro:~# uname -a
Linux liliput-panda 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15
14:00:54 UTC 2011 armv7l armv7l armv7l GNU/Linux
root@linaro:~# free -m
total used free shared buffers cached
Mem: 662 538 123 0 14 494
-/+ buffers/cache: 30 631
Swap: 0 0 0
Is there something else that I'm missing here ?
cheers
Ramana
On behalf of the Linaro Infrastructure team I'm pleased to announce the
release of Linaro Image Tools 0.4.5.
Linaro Image Tools offer a set of tools for use with Linaro images.
This release features installing Linaro Android images. These images can
be found on https://android-build.linaro.org/
Please note that Android image support still is considered experimental,
meaning that the command line interface is subject to change.
The source tarball is available from:
https://launchpad.net/linaro-image-tools/trunk/0.4.5
Thanks,
Mattias Backman