Hi
Notes from today's Landing Teams call; also at
https://wiki.linaro.org/LandingTeams/Meetings/2010-09-22
Activity reports below
Cheers,
=== Attendees ===
* Loïc Minier
* Matt Waddel
* Scott Bambrough
* Mounir Bsaibes
=== Agenda ===
* Action items from last meeting.
* Achievements / progress reports
* OMAP3
* Versatile Express
=== Action Items ===
* Matt to post LTP results for Vexpress on linaro-dev@ or on the wiki
* Matt to close uInitrd u-boot-linaro bug (LP #627843)
=== Action Items from Previous Meeting ===
* Torez to check with jcrigby about updated daily build that has fix for LP: #618734
=== Minutes ===
* Action items from last meeting.
* Torez to check with jcrigby about updated daily build that has fix for LP: #618734
. CO
* Achievements / progress reports
* OMAP3
. See activity report
* Versatile Express
* Low hanging fruit: validating audio on Vexpress; seems to be broken, but Matt was told it's expected to work and is trying more stuff out (as suggested by Pavo)
* Getting defconfig added to the upstream kernel
* Worked with plars on getting https://launchpad.net/abrek working; many low-level failures with LTP; not sure which ones are serious or not
* MMC support in u-boot would be helpful for some use cases; impacts flash-kernel
* flash-kernel: might make sense to send udeb changes as well, not only runtime changes; need to make sure they land in Ubuntu
* Very slow boot; need to log a bug for that
* Could be initrd or rootfs
* Seems there's an extra copy of the initrd going on at boot; need to research this a bit more; might be the boot commands; notably for LP #629614
* Loic would love some data on the kernel configs which are needed for Vexpress boards
* Matt needs to investigate the MMC/USB conflict a bit more
* Mounir would like to help more, but isn't sure where he can contribute
* Loic suggests that consolidating information on board status, and describing hw enablement processes would help as they are currently lousely coupled
Activity reports for last week
= Matt Waddel =
== this week ==
* Fixed deploy mechanism for ARM compatiblity
* Refactored u-boot patches to apply to the next branch
* pushed to u-boot
* Fixed bug 637780 - 2nd flash bank problem
* Bug fixing on vexpress - memory issue, initrd on command line
* frame buffer corruption - LP: #633417
* Will Deacon sent a much better cache setup patch - pushed to linaro
kernel
* abrek (QA system) - investigation and setup
* flash-kernel implementation - submitted patch to debian maintainers
* Tried Lorenzo's vexpress arm device-tree kernel
* Device tree defaults don't work with my monitor, but kernel boots
* Upgraded Vexpress to Maverick
== next week ==
* Validate new images and close bugs
* Fix linaro-media-create bugs assigned to me
* Submit flash-kernel review suggestions
* Vexpress enablement test documentation and development
* Start mmc u-boot support
= Torez Smith =
1) Monday morning went to install and boot daily build and found it did not
build over the weekend nor up to today.....added tools/perf package caused
it not to build...opened a bug for this (bug 643462 Linaro build process
fails to generate builds for 20100919 and 20100920 ) . I'm looking for the
daily builds to assure no regression and to pick up the changes I made for
the IGEPv2 networking (bug 618734 [omap/igep] No eth0 with Linaro kernel).
>From the looks of the bug, these changes should be included in the next
daily build
2) finishing up bug 619206 ( GEP task - libertas-firmware not
installed<https://bugs.launchpad.net/linaro-seeds/+bug/619206>) and
looking at bug
622429 ( ethernet device appears as usb0 and not eth0 on beagle XM
boards<https://bugs.launchpad.net/linux-linaro/+bug/622429>).
3) my bug 633338 (no LCD support on IGEPv2 board) was found to be a
duplicate of bug 607250 (omapdss: VDDA_DAC regulator on IGEPv2) which has
a corresponding patch they are pulling in.
4) next step is to look at the powervr driver changes in the "ARM Graphics
Stack on X" Blueprint.
--
Loïc Minier
We've got a few little helper programs that are used in the Toolchain
WG to help things run smoothly. I've done a short write up on them
here:
https://wiki.linaro.org/WorkingGroups/ToolChain/Helpers
Ulrich, this is the build system I mentioned on the call.
Scott/James/Mounir, it's not great, but this gives you an idea of the
tools I'd like to hand over.
-- Michael
Hi all,
I was recently hired by CodeSourcery and have been assigned to Linaro
for the purpose of improving OpenOCD.
Specifically, I will be adding new support for Cortex-A9 SMP, though I
may also make a few improvements to its handling of Cortex-A8 in the
process. If you have experience using OpenOCD in these contexts, let me
know if you have any specific requests for features or fixes, and I will
try to fold them into my plans.
After this cross-posted introduction, I believe that most of my
correspondence will appear on the Toolchain mailing list, but I wanted
to make sure that everyone knows that they can find me there.
Cheers,
--
Zach Welch
CodeSourcery
zwelch(a)codesourcery.com
(650) 331-3385 x743
This mail is to give an update on the current state of PowerTOP and
PowerDebug tools.
The patch to make PowerTOP work on ARM boards too (by removing the
hardcoded values for these states) has been included in upstream. This
patch has also made it into the Maverick PowerTOP package
(https://launchpad.net/ubuntu/maverick/+source/powertop/1.13-1ubuntu1).
Request you to test this package on whatever hardware you may have
(x86/arm) and report any problems that you may encounter.
PowerDebug is a new tool that we are working on which will provide
some more Power Management related information, like - Regulator,
Sensor and clock domain information. The source code can be downloaded
from my git tree
(git://git.linaro.org/people/amitarora/powerdebug.git) OR from my PPA
(ppa:amitarora/pm-utils). Its still at experimental stage and is under
active development. Feel free to try it out and give your valuable
feedback.
Thanks!
Regards,
Amit Arora
Correct report link updated!
-------- Original Message --------
Subject: Linaro Infrastructure Team Weekly Report (2010-09-09 to
2010-09-16)
Date: Thu, 16 Sep 2010 10:32:12 +0100
From: Ian Smith <ian.smith(a)linaro.org>
To: linaro-dev(a)lists.linaro.org
The weekly report for the Linaro Infrastructure team may be found at:
Status
report:https://wiki.linaro.org/Platform/Infrastructure/Status/2010-09-16
Burndown
chart:http://people.canonical.com/~pitti/workitems/maverick/linaro-infrastr…
The burndown chart is showing that number of work items has increased,
with a number of work items completed. This is showing that the number
of work items to complete is slipping further behind the trend line.
* Merged XML-RPC API and client and various fixes to them
* Got initial set of views into trunk. Currently this adds support
for browsing streams. While simple, it paves the way for more views (the
task is simple and repetitive) as we support authentication, unit tests
and other goodness that made it take longer.
* Got generic databrowser merged. This allows anyone to browse
everything that is in the database (so any bundles/tests that are
already in can be accessed without extra effort). This will act as a
temporary view layer before we can iron out what people actually want
from us.
* "Decide on dependency management approach (debs/buildout/...)": DONE
* "Implement dependency management": DONE.
* HardwarePacks: hwpack-install: landed and fixed a couple things
reported by asac
Please let me know if you have any questions.
Kind Regards,
Ian
I don't understand the page at:
https://wiki.linaro.org/Copyright
I've put the new Toolchain WG web tools up on Launchpad so that others
in the group can get it. It needs a README (fine), license (EPL
apparently), and copyright statement.
I'm paid by Canonical but work for Linaro. The Copyright page says
that new work is (C) Canonical and then the copyright 'flows' to
Linaro. What does this mean and how do I achieve it? What copyright
statement should be on the work and where?
At a different level, how do you apply the EPL to a project? What
text should I have in what files to record the license and copyright?
Is there a standard way of doing this?
-- Michael