Hi,
The Developer Platform team weekly report for 2011-03-10 is now
available and can be found at:
https://wiki.linaro.org/Platform/DevPlatform/Status/2011-03-10
The report is also reproduced in full below.
Regards,
Jamie.
--
Linaro Release Manager | Platform Project Manager
--
* Period: (20110303-20110309)
* PM: JamieBennett <jamie.bennett(a)linaro.org>
* Past reports : https://wiki.linaro.org/Platform/DevPlatform/Status
* Burndown information : http://status.linaro.org/linaro-foundations.html
== Key Points for wider discussion ==
* The process to produce and upstream ALIP cross-compile fixes is slow,
what can we do to speed this up?
* Multi-arch changes are still landing to the Ubuntu archive, lots of
testing is needed here.
* Panda display issues are now resolved so more testing of images on
the Panda board is possible.
* The Nano image needs to be slimmed down further. Tom has proposed
some changes but others need to review and comment on them.
== Team Highlights ==
* LTTng 0.245 has been ported to the linux-linaro-2.6.38 kernel. The
changes are available at:
http://git.linaro.org/gitweb?p=people/aviksil/linux-2.6-lttng-linaro.git;a=…
* Work continues on parts of kdelibs with the GL dependency removed
from libplasma and kdebase-window-manager updated.
* After many investigations the Panda non-display issue (bug:728603)
has a fix. A config option change will enable the display to work with a
knock-on effect of other bugs such as bug:720055 also being resolved.
* A thumb2 enabled kernel build has been turned on after work by both
the Kernel Working Group and the Developer Platform team.
* Linaro's smallest full image, Nano, got reduced in size to 125mb
installed. Proposed changes to eventually get closer to the 64mb
installed target are currently in discussion.
* libjpeg-turbo got further work this week as lintian errors were
fixed.
* Several more packages have been fixed for cross-compilation in the
Ubuntu archive.
* dpkg support for multiarch library installation is in the Ubuntu
archive but needs another upload due to changes in the planned dpkg
database format. There has also been some patches submitted to apt for
the major multiarch blocker bugs as the team continue towards a true
multi-arch solution.
* Cross toolchain packages got reuploaded to the archive fixing recent
issues.
== Upcoming Deliverables ==
* Beta Freeze 2011-03-24
* New build of Linaro Linux kernel
* systemtap v1.3 + cherry-picked fixes
* apt fixes to Ubuntu
* New dpkg to Ubuntu that implements support for the final multi-arch
library paths
== Risks / Issues ==
* '''MEDIUM IMPACT''': Peter Pearce reports that bootstrapping & making
cross-compile patches upstreamable are slowing the rate of package
fixing. The (current) alip package list will not be complete for beta
freeze.
* '''LOW IMPACT''': All multiarch work is landing past feature-freeze.
Requires exception approval from the Ubuntu and Linaro release teams.
== Miscellaneous ==
* Wiki pages of note this week:
* http://wiki.debian.org/DebianBootstrap
* https://wiki.linaro.org/Chromiumos/ChromeosWm
On Thu, Mar 10, 2011 at 8:59 AM, Guillaume Leteller
<guillaume.letellier(a)arm.com> wrote:
> Hi
>
>> In the developer platforms team we're working on getting the
>> linaro-nano image so that it is considerably smaller.
>
> Brilliant!
>
>> Some highlights to nano:
>> * The linaro-image boots just as our linaro-headless image did
>> (upstart and friends)
>> * it can be updated, or additional pkgs installed via apt-get
>> * networking works
>> * busybox is in use tho not necessarily universally
>> * ureadahead, python, have been removed
>> * docs have been removed
>> * linux-firmware has been removed (binary kernel firmware blobs)
>> * locales is remove
>>
>> Installed image is 125 Megs. (Down from 290 Meg) We're on the cusp of
>> being able to fit into 128 megs of flash.
>
> Isn't it quite big for a "Nano" image? It looks like a size for a
> 'developer' version.
> Do we know why it's so big?
It's a process. I'd like to get down to 64 Meg but one step at a time,
128 Meg being a first step. I feel this is reasonable as both my
Beagle C4 and Beagle Xm both have 256 Meg of NAND.
> In comparison, ARM developed AEL/ALIP
> (http://www.linux-arm.org/LinuxFilesystem/AELFileSystemPage) and we were
> hoping to use Linaro's Nano image from now on.
> The size of the AEL/ALIP minimal version (busybox, ssh) was only 25MB
> (compressed - Cramfs). And the version with X11 and a desktop was 55MB.
Indeed.
> Those images are useful for development boards with 64MB of flash or when
> using CPU models.
Do you have some boards in mind that only have 64Meg of Flash?
>> > 3) linaro-media-create should have some kind of option (--nano) to
>> > clear out apt caches (saves ~40 meg of space)
>>
>> If you want this it should be an easy change to make.
>
> This looks good if it's an easy change.
>
> Does it address the problem with Modules and firmware?
> Is it possible to get an image without Hwpacks?
>
> Regards,
>
> Guillaume
Thanks for the info and feedback Guillaume.
Regards,
Tom
Hi,
If I mess up the u-boot in my efikamx smart book how can I install a new one?
I tried booting with an SD-card image from
http://www.powerdeveloper.org/asset/by-id/116. I guess this only works
if I have a working u-boot in place.
I don't have the serial/JTAG connector. Is this what I need in order to recover?
Thanks,
Per
Hi all,
Per Nicolas' request, I've compiled a list of all patchsets needed to
get functional display on the Pandaboard. There are 35 patches in all,
over 6 series, plus one patch for the board file to enable the DVI
support.
I've set up two branches (against v2.6.38-rc4, and against the head of
linux-linaro-2.6.37 as of today) to make it easy for people to extract
and test these.
They are available in my git tree here:
git://dev.omapzoom.org/pub/scm/anand/linux-omap-usb.git
in the display-patches-for-v2.6.38-rc4 and
display-patches-for-linaro-37 branches respectively.
I've updated the bug report for this issue (Bug #707038) with links to
the component series, as well as the link to my tree above.
(I'll make sure these two branches stick around - at least as a
reference - until the patches make it upstream).
@Nicolas,
None of these have been queued up by the respective maintainers yet,
so they aren't in linux-next as of today. However I believe there are
no outstanding review comments for these.
I can send a pull request for these if it's okay with you. Let me know
if you need them based off any particular tag/commit/branch.
- Anand
Enclosed you'll find a link to the agenda, minutes and actions from the
Linaro toolchain working group weekly meetings of March 07 & March 09,
2011.
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-03-07https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2011-03-09
== Summary ==
* Did the 2011.03 releases of Linaro GCC 4.5, 4.6, Linaro GDB 7.2, and
Linaro QEMU
* Linaro QEMU now contains Versatile Express support.
* First couple of optimised string routines are now in Ubuntu
* Continuing with benchmarks.
* Re-run against FSF trunk to see the areas we can improve on
* Continuing progress on SMS optimisation, GDB correctness, and libffi
Regards,
Mounir
Enclosed you'll find a link to the agenda, minutes, actions and IRC logs
from the
Linaro kernel working group weekly meetings of March 07, 2011.
https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2011-03-…
== Summary ==
* Bug reviews
* Google Summer of code
* Patches submission reminder
* Trying to get first pass at the kconfig fragments work in such a state
that can be sent for initial review
* Sending out the V2 patch for MX51 dt support
* Will merge the MX53 loco board support patchset soon.
* Sent out v13 of the clk-common patches, tweaked them for
!CONFIG_USE_COMMON_STRUCT_CLK compatibility, and sent out v14
* A backlog of patches being reviewed to comment on and/or pick up into
devicetree/arm, expect updates later this week
Regards,
Mounir
Ubuntu/natty got some cross toolchain updates recently so it is
installable again. This gave me some free time to work on improvements.
And this mail is an attempt to summary it and to provide some
ideas/questions.
= Introduction =
During Emdebian sprint it was decided that my source packages will be
used in Debian to provide cross toolchains for users in archive itself
(as now Emdebian team autobuilds them into separate archive). We created
crosstoolchain project [1] at Alioth and plan to keep Debian branches in
git.debian.org repository [2].
= Existing branches =
Speaking of branches - there are several ones in my git repository [3]
and some of them are also present as Bazaar branches on Launchpad. This
list follows:
debian/experimental/armel-cross-toolchain-base
debian/experimental/gcc-4.5-armel-cross
debian/experimental/gcc-4.6-armel-cross
debian/unstable/gcc-4.4-armel-cross
Those ones can be used to provide cross toolchain for Debian. First one
is really ugly as for now it contains a copy of eglibc and linux-2.6
packaging. I have to report few patches [4][5][6] for both components to
get this situation sorted. GCC ones do not have any such problems.
ubuntu/natty/armel-cross-toolchain-base
ubuntu/natty/gcc-4.4-armel-cross
ubuntu/natty/gcc-4.5-armel-cross
Those ones will be soon sent for review/merge/upload into Ubuntu.
ubuntu/not-used/gdb-armel-cross
Superseeded by gdb-multiarch package - gdb 7.2-1ubuntu8 or newer
required.
ubuntu/ppa-backport/armel-cross-toolchain-base
ubuntu/ppa-backport/gcc-4.5-armel-cross
ubuntu/ppa-backport/patches
Those branches are used to generate packages in Linaro toolchain
backport PPA [7]. "/patches" branch keeps all patches which I use to
alter components.
= Status =
During sprint I merged 3 branches of armel-cross-toolchain-base into one
set of rules so today there are not differences between Ubuntu ones and
Debian one contains extra debian/packaging directory with copies of
eglibc/debian and linux-2.6/debian dirs. Generation of debian/control
file is now inside of debian/rules so differences in build dependencies
are handled. Switch between Ubuntu and Debian is sorted by using
"lsb_release" (idea taken from gcc-4.5) and PPA build can be enabled by
"touch debian/ppa".
= Ideas =
There was idea to generate just one source package from this (so it
would be debian/experimental/armel-cross-toolchain-base branch) and
generate all versions from it. I think that this will work but first we
need to get Debian version into state which will be acceptable for
inclusion into archive.
= Problems =
Main problem is debian/packaging/ directory in Debian version. I need
review of [4] patch and then will report a bug against eglibc.
= Multiarch versions (future) =
When cross build dependencies will be working then we will get rid of
armel-cross-toolchain-base package and replace it with
binutils-armel-cross (or extend binutils-multiarch to contain "as" and
rest of missing binaries).
1. http://alioth.debian.org/projects/crosstoolchain/
2. http://git.debian.org/?p=collab-maint/cross-toolchain.git;a=summary
3.
http://git.linaro.org/gitweb?p=people/hrw/cross-toolchain-packaging.git;a=s…
4. http://42.pl/u/2zj4
5. http://42.pl/u/2zj5
6. http://bugs.debian.org/611382 (merged into
http://bugs.debian.org/550776 one)
7. https://launchpad.net/~linaro-maintainers/+archive/toolchain
Hi,
I am trying to prepare an MMC card to boot up Panda with Linaro daily
build image.
I downloaded linaro-image-tools from:
https://launchpad.net/linaro-image-tools
I installed all dependencies mentioned in the README and tried to run
linaro-media-create like below:
sudo ./linaro-media-create --rootfs ext3 --mmc /dev/sdb1 --binary
/home/a0393566local/linaro/headless/linaro-natty-headless-
tar-20110206-0.tar.gz --hwpack /home/a0393566local/linaro/hwpack
/hwpack_linaro-panda_20110206-0_armel_supported.tar.gz --dev panda
However, it crashes immediately with the following dump:
http://pastebin.com/SV78dP8L
Any idea what could be going wrong?
Thanks,
Aneesh