Multimedia

Revision 9 as of 2010-10-28 19:32:57

This page is here to collect together proceedings from sessions as part of the 'Multimedia' track at the Natty UDS in Orlando, Florida.

Please add proceedings by doing the following:

Add a new section with the name of the session.
Add the outcomes of the session as a collection of bullet points. The goal of the proceedings is to really focus on decided outcomes, so please try to keep them crisp.

Thanks!

Contents

Proceedings

Agreed Major Usescases for JPEG Decoder: Browser (many small images), Image Gallery (Large Images)
Selection of Software JPEG Decoder for optimization: IJG's Libjpeg
JPEG Interface to be exposed: libJPEG (& OpenMAX possibly)
Combining H/W & S/W Decoder: Decided to do it with simple GLUE layer over libJPEG.
Runtime Selection of SoC specific execution path: Agreed to have only compile time support.
ARM+NEON Optimizations Ideas: Agreed to not do SMP-aware codec, Agreed for doing no optimization for ARM11 and older processors.

If it makes sense, seed(s) could be based on the upcoming developer seed
Research should be done to find and include tools for analysis of video/audio streams/content
nfsclient needs to be included for easy access to test content
Support for application logging needs to be included for those applications that have a logging feature
There should be enough content for test / validation either as part of the image or accessible
It was suggested that the landing teams should be the team to assemble demo materials for specific boards with the help of the Multimedia WG
There should be enough support included to support automated testing both running and reporting results

cairo is not the right place to handle runtime selection. It is up to the higher-level code to decide and use the best cairo facilities.
We should implement a GLES2 backend, by preferably making the current experimental GL backend GL/GLES2 "agnostic". We should measure and publish the performance benefits.

Notes

it might be useful to have a unity seed depending on the switch to compiz, OpenGLES
developer tools should be included in a seed with all dev packages, compilers, build essentials, automake, enough to build gles, graphical applications
alf suggestioned the following seed layout
- x11-base + dev-base -> gfx-dev + gfx-packags
There should be two flavours, dev and test/demo (meant to boot, run simple demo)
spandex - python based framework for gles benchmarks by nokia
packages should include enough to build gles, applications and run them dev versions of mesa, x, freeglut, extention wrangler, dri experimental (for gallium), meego-touch (maybe), cairo, cairo-perf, gtk-perk, mesa-demos
- could have multiple window managers etc installed but allow for easy switching for the purposes of development
size constraints only a consideration for the purposes of a head (such as alip) which has a goal to fit into 64M flash
automated test images should support automated test running and result reporting in general

Actions

[action] connect with team defining development seed (tgall-foo)
[action] need to push fix for germinate for mulitple PPAs (alf)
[action] Jesse Barker to push graphics dev packages to tgall-foo
[action] Jesse Barker will work gles performance tools list and supply input
[action] check / remove SOC specific headers / images from headless, move to hwpack (tgall-foo)