Greetings,
Enclosed you'll find a link to the agenda, notes and actions from the
Linaro User Platforms Weekly Status meeting dated November 17th held in
#linaro-meeting on irc.freenode.net at 13:00 UTC.
https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-11-17
Status Summary:
- blueprint and spec work review continues in advance of public
reviews for Graphics on the 19th and Multimedia on the 23rd
- updated clutter and mutter packages with EGL TFP patches posted to
ppa:asac/armel1
- texture_from_pixmap_glesv2 EGL TFP example pushed to upstream mesa-demos
- No SIMD copy of libjpeg-turbo created as part of understanding
acceleration infrastructure
- Issue created for runtime detection of NEON in skia created
upstream, no feedback yet
- omxil bellagio packaged
- Investigation of ogre using GLES2 rendering engine on arm begun.
Regards,
Tom (tgall_foo)
User Platforms Team
"We want great men who, when fortune frowns will not be discouraged."
- Colonel Henry Knox
w) tom.gall att linaro.org
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
FYI, I've set up a tree with my currently posted patches, with
branches currently as follows:
git://git.linaro.org/people/dmart/linux-2.6-arm.git
Upstreamable branches:
* master : base branch in sync with linus' tree
* arm/* : topic branches for ARM architecture support stuff
* arm-all : merge branch of arm/* (excluding arm/development/ branches)
Changes appearing in the above branches has either been posted on
upstream lists or is about to be posted.
Development branches:
* development/* : development versions of upstreamable branches.
These are more volatile and may not have been discussed upstream.
Dirty branches:
* dirty/* : hacking branches which are considered unsuitable for upstream
* dirty-all : merge of all interesting changes including dirty ones
The dirty* branches are not ready for upstreaming:
Don't pull these branches without good reason.
Do we have a systematic place to document the contents of git trees?
I put the above text in linux-2.6-arm.git/description, but gitweb only
seems to show the first line.
I'm a bit of a newbie to this, so any comments welcome regarding how
I've set this up.
Note: If you want to build a Thumb-2 kernel, you'll probably need
dirty/gas-adr-bug, which contains a fix which is needed when building
a Thumb-2 kernel due to a bug in gas.
Cheers
---Dave
All,
The weekly report for the Linaro Infrastructure team may be found at:-
Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-11-18
Burndown chart:http://people.canonical.com/~pitti/workitems/maverick/linaro-infrastr…
The Infrastructure related blueprints, of which currently there are 4 active ones (4 from the last report), are showing that there are 8 work items in progress (11 last report), and 11 work items to undertake (12 last report).
arm-m-validation-dashboard; 0 work items completed since last report; 3 in progress; 7 to do
arm-m-image-building-console; 1 work items completed since last report; 3 in progress; 3 to do
arm-m-automated-testing-framework; no change in status from last report; 1 in progress; 0 to do
arm-m-testsuites-and-profilers; no change in status from last report; 1 in progress; 1 to do
The focus for the team in the past week has remained on preparing Blueprints for the next cycle and holding the review conference call on Monday (2010-11-15).
The team had two new members join this week.
Specifics accomplished this week include:-
* A number of new PPAs were produced this week, including an improved linaro-json package and a stable API for working with dashboard bundles.
* Work started on ImproveLinaroMediaCreate
* Two bugs were fixed for Linaro Image Tools covering apt-get running in rootfs and replacing "sfdisk -l"with "fdisk -l" to give more useful information.
Please let me know if you have any comments or questions.
Kind Regards,
Ian
As part of the Power Management Work Group, I have been developing a
new tool called PowerDebug which can show users/developers information
on regulators, senors and clock tree. Its time now to package it for
Ubuntu (since, Linaro will pick up the package from Ubuntu repo.). We
also plan to host a project in LaunchPad for this tool.
I am new to Ubuntu and debian way of packaging. Still, have given a
shot at packaging PowerDebug and have put it in my git tree hosted at
: git://git.linaro.org/people/amitarora/powerdebug.git in the branch
called "debian". The "master" branch has only the source code for the
tool.
If you have fare idea about .deb packaging, I will request you to
please review these files and suggest any changes that may be
required. I have also uploaded this under my ppa
(ppa:amitarora/pm-utils).
Thanks!
Regards,
Amit Arora
Greetings,
Enclosed you'll find a link to the agenda, notes and actions from the
Linaro User Platforms Weekly Status meeting dated November 10th held in
#linaro-meeting on irc.freenode.net at 13:00 UTC.
https://wiki.linaro.org/Platform/UserPlatforms/WeeklyStatus/2010-11-10
Status Summary:
- clutter 1.2 EGL_KHR_image_pixmap support for clutter and unity
finished and verified with omap4
- ux500 support landed for release in linaro-image-tools; ux500
release hwpack validated for all heads
- first set of blueprints of multimedia and graphics WG submitted for review
- public review of plans for multimedia WG on Nov 23; for graphics WG on Nov 19
- first experiments on a linaro-development image conducted
- ST-Ericsson succeeded to compile their multimedia pack with Linaro toolchain
Regards,
Tom (tgall_foo)
User Platforms Team
"We want great men who, when fortune frowns will not be discouraged."
- Colonel Henry Knox
w) tom.gall att linaro.org
w) tom_gall att vnet.ibm.com
h) tom_gall att mac.com
I'd like to announce that Launch Control (the project) is being packaged
and separated into dedicated launchpad projects/code trees.
I managed to set up two PPAs to make everyone's life easier:
* linaro-infrastructure/launch-control
* linaro-infrastructure/launch-control-snapshots
The first one is designed to hold *releases*, currently it's empty as
there are no new releases yet and old releases are not packaged.
The second one (which I encourage you to use if you are interested in
launch-control) contains daily builds of the following packages:
* python-linaro-json
* python-linaro-dashboard-bundle
* launch-control-tool
The list of packages will grow as I get the whole server decomposed and
packaged. That's right, currently the "dashboard" is not available as a
debian package just yet.
Just as a quick reminder, if you want to add a PPA to your system from
command line you can use add-apt-repository, like this
$ sudo add-apt-repository ppa:linaro-infrastructure/launch-control-snapshots
$ sudo apt-get update
$ sudo apt-get install launch-control-tool
Thanks
Zygmunt Krynicki
Hi all,
thanks to the restless efforts of the User Platforms team and friends,
we have concluded our clutter/mutter/clutk/unity work for the previous
cycle. Although we didn't get to the point of providing an ultra smooth
user experience, this is still a great success and more than we hoped
for at the beginning of the cycle.
You can find all the related packages at ppa:asac/armel1.
For those who are wondering, the fact that Unity will now move to compiz
does not invalidate our efforts at all. Unity was just a means to an
end, a way to recognize some of the ingredients that are needed to
provide a smooth user experience on ARM (and GLES2.0 platforms in
general).
Some highlights from our efforts:
* We clearly communicated our technical and distribution related needs
to upstream clutter and contributed patches to support our goals. As
a result, clutter is progressively becoming more friendly to
distributions that need to ship multiple backends and perform runtime
selection.
* We standardized on and provided a proof-of-concept implementation
for accelerated WM compositing using the EGL_KHR_image_pixmap and
GL_OES_EGL_image extensions for EGL/GLES2.0. This is a critical
feature for providing a smooth user experience on GLES2.0 based
platforms.
* We provided vendors with a real-world test case that can be used
to exercise their drivers on.
For the next cycle we are moving away from active development on clutter
and mutter, but we will still keep an eye on them (esp. clutter). We may
even be able do some more work on them if we have the resources and
there is a high demand for it.
Thanks,
User Platforms team
Lee,
I created a page on how to package a kernel. There are some hacks
here that would not be appropriate when packaging a kernel for a real
upload but should work fine for landing team testing.
https://wiki.linaro.org/PackageYourOwnKernel
John