Delivery to 11.11 - which components delivered what

Priority

Headline

Acceptance

Notes

Graphics

glmark2

https://blueprints.launchpad.net/glmark2/+spec/glmark2-release-2011.11

Essential

Release glmark2 2011.11

For Ubuntu, glmark2 2011.11 is installable from the overlay PPA and works correctly on panda-leb Ubuntu. For Android, glmark 2011.11 is built successfully as part of the Android build and works correctly on panda-leb Android

DONE

https://blueprints.launchpad.net/glmark2/+spec/glmark2-bump-mapping

High

Benchmark for bump-mapping using a height map

Benchmark runs successfully as part of default benchmarks on panda-leb Ubuntu and Android

DONE

https://blueprints.launchpad.net/glmark2/+spec/glmark2-validation

Medium

glmark2 supports validation of all default benchmarks

All glmark2 default validation tests pass on both desktop (mesa) and panda (sgx)

DONE

https://blueprints.launchpad.net/glmark2/+spec/glmark2-code-cleanup

Low

Ensure glmark2 code is in top shape

Code is easier to navigate and understand and continues to compile

DONE

Linaro Graphics WG LAVA tests

https://blueprints.launchpad.net/linaro-graphics-tests/+spec/lava-tests-run-daily

High

Linaro Graphics WG tests/benchmarks running daily on produced linaro images

Linaro Graphics WG test results for daily runs are available in the lava web

Good progress, bundled streams are here, currently ensuring everything runs smoothly - no component release just LAVA related work

Hook performance events from GPU

https://blueprints.launchpad.net/linaro-graphics-misc/+spec/engr-profiling-gpu-perf-2011.11

Medium

Hook performance events from GPU

Hook performance events from GPU

DONE - no component release just enablement via kernel code for now




Upcoming deliverables - 11.12

Priority

Headline

Acceptance

Notes

Graphics

glmark2

https://blueprints.launchpad.net/glmark2/+spec/glmark2-bilinear-filtering-shader

Medium

Benchmark for implementing bilinear filtering in shaders

Benchmark can run successfully on all available platforms (desktop and embedded)

Not released yet

glproxy

https://blueprints.launchpad.net/glproxy/+spec/glproxy-egl-virtualization

Medium

Adding EGL support to glproxy will allow applications to delay choosing to use it until run-time, just like GLX is supported now

Applications can link with glproxy and decide at run-time to use EGL or GLX

Not released yet

https://blueprints.launchpad.net/glproxy/+spec/glproxy-support-glcompbench

Medium

glproxy is a library that allows applications to delay linking with OpenGL or OpenGL ES2 until run-time

Applications can link with glproxy and decide at run-time to use EGL or GLX

Not released yet

Linaro Graphics WG dashboard

https://blueprints.launchpad.net/linaro-graphics-dashboard/+spec/linaro-graphics-dashboard-glmark2

High

Visualization of glmark2 results in dashboard

The pages are accessible in the production instance of the validation web site, and display the results correctly

Not released yet

glcompbench

https://blueprints.launchpad.net/glcompbench/+spec/glcompbench-glproxy

Medium

glcompbench is a tool to benchmark window compositing operations

glcompbench uses glproxy to choose the backend (OpenGL or OpenGL ES2) at runtime instead of building a different executable for each one

Not released yet also depends on bug 855524

Linaro Graphics Miscellany

https://blueprints.launchpad.net/linaro-graphics-misc/+spec/apitrace-gles2

Medium

Ensure proper apitrace support for OpenGL ES 2.0

We can capture and playback a trace of glmark2 on panda

Not released yet

https://blueprints.launchpad.net/linaro-graphics-misc/+spec/gpu-power-management-analysis

Medium

Analyze needed GPU, PM and GPU interface for GPU power management

Analysis in the wiki

Not released yet


Highlights

  • Based on the meeting last week with DX side: no changed lately on NUX. openGLES code has been merged, and believed to be functional and working. At the moment doing more testing on NUX. There is a shift in DX to accept branches after more testing, much of which is automated.
    • In the future there is more need for testing for functional verification and also regression testing
    • Specification related to the tests was requested from Nux maintainer. For the automation tests there are simulations of events such as keyboard events as well as mouse movements or clicks so that aspects of the graphical components are tested (for the UI aspect). The tests for the graphics stack have not been decided yet.
    • For the Linaro side what is important is that DX team want to have a test for every major feature/release related to openGLES. New features should be accompanied by test code, covering the functionality as we well as regression cases.
      • Admittedly there is still a definition pending on DX side about what coverage to provide, not every submission will need a new test necessarily. This is still being decided at the DX team level, and they will communicate with Linaro on the process (still undefined on wk47)
  • Daily benchmarks running on LAVA:
  • Starting in 11.12 to analyse the power management work for Graphics
  • Moved all Launchpad projects for Graphics WG to use trunk as their active series of development

Risks / Issues

Impact

Since

Risk

Mitigation

Status

Medium

2011-11-23

Specification for testing needed at DX is not yet completely shared with Linaro, could cause delays when pushing our code to relevant upstream projects as we will need to provide tests

Requested the specification already, may need to discuss in a meeting about the plans from all sides

outstanding

WorkingGroups/Middleware/Graphics/Status/2011-11-23 (last modified 2011-11-28 10:13:32)