| OLD | NEW |
| 1 Name | 1 Name |
| 2 | 2 |
| 3 CHROMIUM_gpu_memory_buffer_image | 3 CHROMIUM_gpu_memory_buffer_image |
| 4 | 4 |
| 5 Name Strings | 5 Name Strings |
| 6 | 6 |
| 7 GL_CHROMIUM_gpu_memory_buffer_image | 7 GL_CHROMIUM_gpu_memory_buffer_image |
| 8 | 8 |
| 9 Version | 9 Version |
| 10 | 10 |
| (...skipping 33 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 44 Returns a unique identifier for the image that could be used in | 44 Returns a unique identifier for the image that could be used in |
| 45 subsequent operations. | 45 subsequent operations. |
| 46 | 46 |
| 47 INVALID_VALUE is generated if <width> or <height> is nonpositive. | 47 INVALID_VALUE is generated if <width> or <height> is nonpositive. |
| 48 | 48 |
| 49 INVALID_ENUM is generated if <internalformat> is not one of | 49 INVALID_ENUM is generated if <internalformat> is not one of |
| 50 RGB or RGBA. | 50 RGB or RGBA. |
| 51 | 51 |
| 52 INVALID_ENUM is generated if <usage> is not READ_WRTIE_CHROMIUM. | 52 INVALID_ENUM is generated if <usage> is not READ_WRTIE_CHROMIUM. |
| 53 | 53 |
| 54 On OS X, driver bugs prevent the usage of memory buffers with RGB internal |
| 55 format. As a workaround, the created GpuMemoryBuffer will always have |
| 56 internal format RGBA. The caller is responsible for handling this |
| 57 appropriately. The only support provided by this extension is that calls |
| 58 that require parameter validation (such as copyTexImage2D and |
| 59 copyTexSubImage2D) will perform paramter validation as if the internal |
| 60 format were RGB. |
| 61 |
| 54 Errors | 62 Errors |
| 55 | 63 |
| 56 None. | 64 None. |
| 57 | 65 |
| 58 New State | 66 New State |
| 59 | 67 |
| 60 None. | 68 None. |
| 61 | 69 |
| 62 Revision History | 70 Revision History |
| 63 | 71 |
| 64 9/29/2014 Documented the extension. | 72 9/29/2014 Documented the extension. |
| 73 4/12/2016 Added details of OS X RGB workaround. |
| OLD | NEW |