User:Jprosevear/GfxInternUpdate: Difference between revisions

Jump to navigation Jump to search

User:Jprosevear/GfxInternUpdate (view source)

Revision as of 18:29, 30 May 2011

460 bytes removed ,  30 May 2011
→‎Intern Projects
Line 28: Line 28:
| ''TBD''
| ''TBD''
| joe/bholley
| joe/bholley
|-
| Do YCbCr/YUV->RGB conversion of JPEGs on the GPU
| When we're using hardware-accelerated layers, we can reduce the amount of work we need to do on the CPU by decoding JPEGs to YUV only, uploading those channels to the GPU, and then converting the YUV to RGB in a shader.<br><br>'''Note''': This is likely not a good project to start before we have a fully colour-managed pipeline or Emerald is complete.
| ''TBD''
| joe/jrmuizel/mattwoodrow
|-
|-
| WebGL Optional Features
| WebGL Optional Features
Line 61: Line 56:
| jrmuizel
| jrmuizel
|-
|-
| SVG Filter Hardware Acceleration
| SVG Filters on GPU
| Mozilla currently supports SVG filters, however these are currently implemented using software rendering on the CPU.  This is the case even when hardware acceleration is used for general 2D rendering (i.e., Direct2D).  SVG filter support should be extended for hardware acceleration using HLSL shaders to avoid readbacks. The biggest challenges here will be allowing arbitrary chaining of filters, as well as making it possible to avoid reimplementation once we need to support OpenGL shaders too.  
| Mozilla currently supports SVG filters, however these are currently implemented using software rendering on the CPU.  This is the case even when hardware acceleration is used for general 2D rendering (i.e., Direct2D).  SVG filter support should be extended for hardware acceleration using HLSL shaders to avoid readbacks. The biggest challenges here will be allowing arbitrary chaining of filters, as well as making it possible to avoid reimplementation once we need to support OpenGL shaders too.  
| ''TBD''
| ''TBD''
Jprosevear
761

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/313856"

Navigation menu