Hi all,
in some of the blueprints I am following, I have noticed that many work
items updates (e.g. to DONE/POSTPONED/BLOCKED) are not accompanied by
any additional information. Of course, not all work items need
more information, but some are meaningless to an external viewer
without it.
This is a general observation across Linaro and I am as guilty as any.
As an example, consider the following (semi-fictional) work item
updates:
+ Add Qt tracing support for pixmaps: POSTPONED
+ Create a bazaar branch for libX: DONE
+ Select and port an application to GLES2: DONE
+ Test that the application functions correctly on ARM: BLOCKED
These updates raise many questions:
* Why was Qt tracing for pixmaps postponed?
* What is the exact location of the published branch?
* Which application was selected for porting?
* Where can I find the ported code for the application?
* Why is the application test blocked?
Such information is usually placed at the top of the whiteboard, like
this (at least this is how I am doing it):
[alf May 8]: Postponed work on Qt pixmap tracing because it turned
out we can trace Qt/Webkit without it, so it is not considered critical anymore.
[alf May 10]: Uploaded branch to lp:libX
[alf May 10]: Selected application Y for porting to GLES2
[alf May 12]: Finished porting Y to GLES2 and uploaded it to
http://git.linaro.org/...
[alf May 13]: Blocked on testing the ported application Y because of an
issue (LP: #666666) with the 3D drivers for chipset Z.
In conclusion, I would like to encourage more verbosity in our updates,
so that others can easily follow and appreciate all the great work that
we are doing.
Thanks,
Alexandros
Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'm
seeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120
seconds.
[ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 1681.356597] INFO: task kworker/0:0:1030 blocked for more than 120
seconds.
[ 1681.367187] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
root@linaro:~# uname -a
Linux linaro 2.6.38-1002-linaro-omap #3-Ubuntu SMP Fri Apr 15 14:00:54
UTC 2011 armv7l armv7l armv7l GNU/Linux
I'd like to find out what that task is meant to be doing and why it is
getting blocked. I haven't been able to notice anything negative in my
use of the system (downloading and installing packages, editing files,
running cpuburn and stress).
Thanks,
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://launchpad.net/~kiko
Canonical Ltd. | [+55 16] 9112 6430 | http://async.com.br/~kiko
Hi,
Available at https://wiki.linaro.org/Platform/2011-05-24
== Attendees ==
* Alexander Sack (asac)
* Fathi Boudra (fabo)
* Ilias Biris (ibiris)
* James Westby (james_w)
* Paul Larson (plars)
* Ricardo Salveti (rsalveti)
* Zach Pfeffer (pfefferz)
== Blueprints drafting and review ==
* rsalveti: it's going well. a review could start tomorrow.
* ACTION: rsalveti/asac/fabo to review the blueprints (4PM UTC).
* plars: he needs to review the drafts of the team members.
* ACTION: plars/asac/fabo to review the blueprints (3PM UTC).
* james_w: everything on track.
* ACTION: james/asac/fabo to review the blueprints (1PM UTC).
* pfefferz: he created work items. Some WIs are missing.
* ACTION: pfefferz/asac/fabo to review the blueprints (2PM UTC).
== Public plan review discussion ==
* REMINDER: slides should be sent to the TSC one week before the PPR
(2011-05-30).
* Q: how to handle cross team dependencies?
* e.g. validation and infrastructure are sharing TRs or android
* Q: organization by TR or team?
* A: team. TL presents team planned work.
* ACTION: james to make a chart how the cross team TRs lead to
individual team work.
* AGREED: share a common format for the presentation to get a
consistent layout across the platform teams. listing TRs, sorted by
priority.
* ACTION: whoever finishes first few slides to send around to agree
on common format/layout. DEADLINE: 2011-05-25
== Release ==
* rsalveti: going well but some issues to fix.
* final kernel for 11.05 to deliver
* memory missing caused by device tree
* omap3-X11 hwpack misrenders LP: #787054
* ACTION: fabo to mention the memory issue on the release notes.
* asac: release LEB for panda only. Ubuntu and Android should refer
to latest stable release for LEB platforms and to latest daily for LEB
platforms.
* ACTION: fabo to update the main website download page.
* plars: validation team is going to release the source code for their work.
* james_w: infrastructure is going to release the source code for their work.
* ACTION: plars/james/asac/fabo to plan when and how. The discussion
will continue after 11.05 release.
* asac: presentation of the release website layout proposal.
* ACTION: fabo to send a mail presenting the layout and get feedback.
Cheers,
Fathi
--
Linaro Release Manager | Platform Project Manager
Hi all,
When debugging video playback performance issue, we found that pulseaudio is
eating up 100% cpu time. Just in case someone else is having the samilar issue,
please let know.
We are using ubuntu-desktop, snapshot, found this issue at least w/ 0425 image.
Thanks
- eric
Hi,
Linaro Developer Platform team organises every week (Wednesday 14:00 -
18:00 UTC)
an ARM porting Jam. The idea is to gather all developers together to
fix userspace
portability issues across the board. The list of bugs being worked on
is at launchpad:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue
Interested in making the software in Ubuntu run better on ARM? Join us on
the #linaro channel on irc.linaro.org tomorrow!
Cheers,
Riku
Hi,
During LDS we agreed to provide prebuilt Linaro images at our
milestones[1], for users who can't/won't run linaro-media-create. One
thing we forgot to discuss, though, is if it's worth doing so for all
image types or just for the LEB(s).
Our downloads page (http://www.linaro.org/downloads/) has 4 different
image types, but the email for weekly testing, for example, lists only
UbuntuDesktop as official and the others as community images. More
importantly, though, I'm not sure the people who just want to try Linaro
quickly will be interested in anything other than UbuntuDesktop at this
point, so we might as well avoid the extra work to provide images that
are unlikely to be of any use.
Can anybody think of other reasons why we should provide images of all
types?
[1] https://wiki.linaro.org/Platform/Infrastructure/Specs/PrebuiltImages
--
Guilherme Salgado <https://launchpad.net/~salgado>
