- Period: (20120220-20120224)
PM: Ilias Biris <email@example.com>
Burndown information : http://status.linaro.org/current/linaro-multimedia-wg.html
12.02 milestone release: as per https://wiki.linaro.org/Cycles/1202/Release/Highlights we have
Patched alsa-lib and pulseaudio with UCM related patches. Patches include fixed alsa-lib bugs causing multiple enable/disable devices/modifiers, added basic HiFi UCM support for i.mx53 and Panda/PandaES, and enabled support for jack detection in UCM for pulseaudio
- NEON optimisation work for realvideo in libav completed--radically increasing the speed for the codec on ARM with benchmarking tests integrated into LAVA infrastructure
- Released libjpeg-turbo 1.2 version, with benchmarking tests integrated into LAVA infrastructure
- For the end to end audio testing, the prototype which was released earlier for x86 testing has now been ported to ARM (pandaboard). To remind, this prototype is a test application intended for automated testing of the audio stack for Ubuntu on a pandaboard end-to-end
Also bug https://bugs.launchpad.net/linaro-ubuntu/+bug/930334 was fixed (resample method corrected for i.mx53)
- CMA LAVA testing scripts were updated for thee v19 of CMA patches
- Also the dmabuf + camera demo was completed, demo was shown at ELC and Connect. Through the demo the codebase patches for drm/dmabuf were rebased on 3.3-rc1. Still missing: v4l2/dmabuf patches rebasing on 3.3-rc1.
- Still some blueprints were not completed:
- Audio for Panda with Linaro Android ICS "just works": this is now blocked on a number of bugs
- UCM for android - has good progress but needs more development to complete. Missing porting tinyhal on pandaboard and getting it to work.
- For the end to end audio test automation, the final piece of work needed is the lava integration
- For LJT: still missing tjbench and tjunittest running inside LAVA validating builds including LJT
12.03 plans are now being put together (a shortlist is in https://wiki.linaro.org/TomGall/DraftPlan/2012.03Plan). The group is changing slightly the way of working with blueprints. A new milestone called "wip" was added (on top of the existing 2012.xy and backlog milestones). The idea is to use wip as a way to indicate work which is ongoing but not yet ready for a milestone release. This is done in hope that it will minimise shifting of blueprints between monthly milestones, whilst also indicating a clear intention and action to work on the specific backlog items (leaving the corresponding blueprints to backlog opaques the action of working on something in preparation for a future release).
WorkingGroups/Middleware/Multimedia/WeeklyReportPast (last modified 2012-03-14 11:14:30)