ARMGraphicsStackOnX

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2010-05-06 14:52:32 →
Size: 2701
Editor: 217
Comment:
← Revision 5 as of 2010-05-10 13:44:58 → ⇥
Size: 2533
Editor: 217
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
== Summary == == BoF Discussion ==
Line 11: Line 11:
This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples.
Line 13: Line 12:
== Release Note == * requirements for graphics drivers for a good X11 experience
* performance benchmarking on X
* 3D story on X and arm
* video/multimedia on X and arm
Line 15: Line 17:
This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)
Line 17: Line 18:
It is mandatory. === Driver Requirements for X ===
Line 19: Line 20:
== Rationale ==  * Kernel driver:
  * Compatibility with kernel 2.6.32 (Lucid) or higher.
  * KMS (Kernel Mode Setting)
  * Compatibility with the userspace libdrm 2.4.18 (Lucid) or higher
  * Support for RandR output hotplug events (so that the xserver receives an event when external screens are connected or disconnected)
  * GEM (Graphics Execution Manager), TTM (Translation Table Maps) or an alternative kernel video memory manager
  * Dynamic front buffer resizing as in -intel's UXA (so that we don't have to set the virtual resolution and restart X when dealing with external screens using high resolutions)
Line 21: Line 28:
This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.  * DDX (X.Org) driver:
  * Compatibility with xserver 1.7.x (Lucid) or higher (1.8.x)
  * Support for RandR 1.3 (especially transformations, scaling, etc.)
  * Use of the E-EDID functions in X.org (this is useful for HDMI)
  * DRI 2 (Direct Rendering Infrastructure) which allows GLX applications to do direct rendering to redirected windows. This makes OpenGL and XV (X video extension) work correctly with compositing managers.
Line 23: Line 34:
== User stories ==  * Multimedia:
  * Support for either VA-API (Video Acceleration API) or VDPAU (Video Decode and Presentation API for Unix) to allow video programs to offload portions of the video decoding process and video post-processing to the GPU video-hardware.
Line 25: Line 37:
== Assumptions ==  * 3D driver:
  * OpenGL 2.1 (or later) compliant driver, more specifically we would like to have the following extensions available:
   * GL_ARB_framebuffer_object
   * GL_ARB_vertex_program
   * GL_ARB_fragment_program
   * GL_ARB_texture_non_power_of_two
   * GL_EXT_stencil_two_side
   * GL_ARB_vertex_buffer_object
  * Support for GLSL
Line 27: Line 47:
== Design == === Performance / Benchmarking ===
Line 29: Line 49:
You can have subsections that better describe specific parts of the issue.  * performance tests
  * 3D tests
   * phoronix-test-suite (openGL based tests)
  * 2D tests
   * gtkperf (to test performance with GTK+)
   * cairo-perf-trace (to test performance of apps which use cairo e.g. firefox) http://cworth.org/intel/performance_measurement/
Line 31: Line 56:
== Implementation ==
Line 33: Line 57:
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

=== UI Changes ===

Should cover changes required to the UI, or specific UI that is required to implement this

=== Code Changes ===

Code changes should include an overview of what needs to change, and in some cases even the specific details.

=== Migration ===

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.

== Test/Demo Plan ==

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

== Unresolved issues ==

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

== BoF agenda and discussion ==

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.		 === Discussion/Notes ===

BoF Discussion

* requirements for graphics drivers for a good X11 experience * performance benchmarking on X * 3D story on X and arm * video/multimedia on X and arm

Driver Requirements for X

  • Kernel driver:
    • Compatibility with kernel 2.6.32 (Lucid) or higher.
    • KMS (Kernel Mode Setting)
    • Compatibility with the userspace libdrm 2.4.18 (Lucid) or higher
    • Support for RandR output hotplug events (so that the xserver receives an event when external screens are connected or disconnected)
    • GEM (Graphics Execution Manager), TTM (Translation Table Maps) or an alternative kernel video memory manager
    • Dynamic front buffer resizing as in -intel's UXA (so that we don't have to set the virtual resolution and restart X when dealing with external screens using high resolutions)
  • DDX (X.Org) driver:
    • Compatibility with xserver 1.7.x (Lucid) or higher (1.8.x)
    • Support for RandR 1.3 (especially transformations, scaling, etc.)
    • Use of the E-EDID functions in X.org (this is useful for HDMI)
    • DRI 2 (Direct Rendering Infrastructure) which allows GLX applications to do direct rendering to redirected windows. This makes OpenGL and XV (X video extension) work correctly with compositing managers.
  • Multimedia:
    • Support for either VA-API (Video Acceleration API) or VDPAU (Video Decode and Presentation API for Unix) to allow video programs to offload portions of the video decoding process and video post-processing to the GPU video-hardware.
  • 3D driver:
    • OpenGL 2.1 (or later) compliant driver, more specifically we would like to have the following extensions available:
      • GL_ARB_framebuffer_object
      • GL_ARB_vertex_program
      • GL_ARB_fragment_program
      • GL_ARB_texture_non_power_of_two
      • GL_EXT_stencil_two_side
      • GL_ARB_vertex_buffer_object
    • Support for GLSL

Performance / Benchmarking

  • performance tests

Discussion/Notes

CategorySpec

Specs/M/ARMGraphicsStackOnX (last edited 2010-05-30 03:40:37 by 65)