New issue
Advanced search Search tips

Issue 886994 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
backer@chromium.org
rjkroege@chromium.org
piman@chromium.org
spang@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task



Sign in to add a comment

RasterDecoder should not use GL API

Project Member Reported by penghuang@chromium.org, Sep 19 
RasterDecoder uses GL API in many places (See[1]). To work with Vulkan, probably we should get rid of them and only use GrContext and ShareImage API.

[1] https://cs.chromium.org/search/?q=api()+file:%5Esrc/gpu/command_buffer/service/raster_decoder.cc+package:%5Echromium$&type=cs

Comment 1 by rjkroege@chromium.org, Sep 19

Cc: piman@chromium.org
Status: Available (was: Untriaged)

Comment 2 by backer@chromium.org, Sep 19 

This definitely needs to be done.

The current dependencies on GL are:
- getting a handle on GPU memory: Currently using gles2::TextureManager. Shareables will help here.
- quickly copying between GPU memory: See CopyTextureCHROMIUMResourceManager

Eventually we want all renderer clients other than WebGL to use RasterInterface instead of GLES2Interface. IIRC, we will probably need to support colour space conversions in RasterInterface for that.
►

Sign in to add a comment