diff options
| author | gman@chromium.org <gman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-19 06:44:39 +0000 |
|---|---|---|
| committer | gman@chromium.org <gman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-10-19 06:44:39 +0000 |
| commit | a3ded6d49e31e7b03926e30ee04bdb74a622ca9a (patch) | |
| tree | c785c8cac83b0e7c30e50dbd24ed650397c59adf /chrome/common/gpu_messages_internal.h | |
| parent | 10156ef03d6985f8c0a9def13b02ad6fc3cee7f9 (diff) | |
| download | chromium_src-a3ded6d49e31e7b03926e30ee04bdb74a622ca9a.zip chromium_src-a3ded6d49e31e7b03926e30ee04bdb74a622ca9a.tar.gz chromium_src-a3ded6d49e31e7b03926e30ee04bdb74a622ca9a.tar.bz2 | |
Add Ability to pass in allowed extensions to GPU contexts.
Questions:
1) Is WebGraphicsContext3D only used for WebGL? Currently
this patch makes that assumption.
2) I started by adding const char* allowed_extensions to
a bunch of functions. Then, at the IPC level added
GPUInitParams. Should I use GPUInitParams everywhere?
3) Is the path for gpu_init_params.h ok?
TEST=unit tests, manually tested WebGL
BUG=none
Review URL: http://codereview.chromium.org/3775014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@63026 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/gpu_messages_internal.h')
| -rw-r--r-- | chrome/common/gpu_messages_internal.h | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/chrome/common/gpu_messages_internal.h b/chrome/common/gpu_messages_internal.h index b95a534..184d8f4 100644 --- a/chrome/common/gpu_messages_internal.h +++ b/chrome/common/gpu_messages_internal.h @@ -10,6 +10,7 @@ // from it via utility_messages.h. #include <vector> +#include <string> #include "base/shared_memory.h" #include "chrome/common/gpu_video_common.h" @@ -23,6 +24,7 @@ namespace IPC { struct ChannelHandle; } +struct GPUCreateCommandBufferConfig; class GPUInfo; //------------------------------------------------------------------------------ @@ -157,9 +159,10 @@ IPC_BEGIN_MESSAGES(GpuChannel) // to a native view. The |render_view_id| is currently needed only on Mac OS // X in order to identify the window on the browser side into which the // rendering results go. A corresponding GpuCommandBufferStub is created. - IPC_SYNC_MESSAGE_CONTROL2_1(GpuChannelMsg_CreateViewCommandBuffer, + IPC_SYNC_MESSAGE_CONTROL3_1(GpuChannelMsg_CreateViewCommandBuffer, gfx::NativeViewId, /* view */ int32, /* render_view_id */ + GPUCreateCommandBufferConfig, /* init_params */ int32 /* route_id */) // Tells the GPU process to create a new command buffer that renders to an @@ -170,7 +173,7 @@ IPC_BEGIN_MESSAGES(GpuChannel) IPC_SYNC_MESSAGE_CONTROL4_1(GpuChannelMsg_CreateOffscreenCommandBuffer, int32, /* parent_route_id */ gfx::Size, /* size */ - std::vector<int>, /* attribs */ + GPUCreateCommandBufferConfig, /* init_params */ uint32, /* parent_texture_id */ int32 /* route_id */) |