summaryrefslogtreecommitdiffstats
path: root/gpu
Commit message (Collapse)AuthorAgeFilesLines
* Move Insert/SignalSyncPoint() to GpuControljamesr@chromium.org2013-10-0212-35/+41
| | | | | | | | | | | This moves InsertSyncPoint() and SignalSyncPoint() to the gpu::GpuControl interface to get a step closer to removing the WebGraphicsContext3D interface. R=piman,sievers Review URL: https://codereview.chromium.org/24925002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226412 0039d316-1c4b-4281-b951-d872f2087c98
* Move more framebuffer state out of ContextState and into FramebufferState.kloveless@chromium.org2013-10-024-47/+59
| | | | | | | | | This will us (in future CLs) to not pass in ContextState into FramebufferManager, but just the FramebufferState. Review URL: https://codereview.chromium.org/25277005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226374 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Disables EXT_discard_framebuffer extension on Vivante GPUs.kaanb@chromium.org2013-10-011-1/+16
| | | | | | | | | | Discarding framebuffer doesn't accept trivial attachments which causes GL errors. On a debug build these errors cause the browser to hang. BUG=299494 Review URL: https://codereview.chromium.org/25416002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226329 0039d316-1c4b-4281-b951-d872f2087c98
* Route GenMailboxCHROMIUM through GpuControlpiman@chromium.org2013-10-0118-103/+71
| | | | | | | | | | | | This allows the fast path to work in GLES2Implementation rather than needing WGC3DCBI. BUG=181120 R=sievers@chromium.org Review URL: https://codereview.chromium.org/24714002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226145 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] Restore EGL Context after collecting GPU infoboliu@chromium.org2013-10-011-0/+45
| | | | | | | | | | | | | | | | In Android, a short lived EGL context is created on the UI thread during start up to collect GPU info. One side effect is that if there is an existing EGL context current, then it is released. This is a problem for Android WebView but may affect Chrome as well. This patch saves and restores the existing current context if there is one. BUG= Review URL: https://codereview.chromium.org/25298003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226104 0039d316-1c4b-4281-b951-d872f2087c98
* GTTF: enable new test launcher for gpu_unittestsphajdan.jr@chromium.org2013-09-302-1/+22
| | | | | | | | | | | | | Note that this is behind a flag for now, --brave-new-test-launcher. Makes gpu_unittests take 3s instead of 10s on my workstation. BUG=299202 R=piman@chromium.org Review URL: https://codereview.chromium.org/25050006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226081 0039d316-1c4b-4281-b951-d872f2087c98
* PPAPI: Make GLES2 calls resilient to bad/dead resources.dmichael@chromium.org2013-09-301-19/+60
| | | | | | | | | | | | | | | | | | | Currently, if PPB_OpenGLES2 is passed a bad resource, or if a bad resource is set prior to OpenGLES2 calls, our code happily dereferences a NULL pointer. This CL tries to address that by handling failure in a way that's consistent with our other Pepper interfaces. It also appears that the "old" approach to locking would end up locking twice per call. Once to get the PPB_GLES2Impl, then unlocked, and then locked again inside the LockingCommandBuffer (meaning that the PPB_GLES2Impl might not actually be valid at the time we dereference it!!). This change simplifies that and removes the old/hacky way of locking. BUG=275815 Review URL: https://codereview.chromium.org/24466004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@226017 0039d316-1c4b-4281-b951-d872f2087c98
* gfx: Create a separate gfx component out of ui.sadrul@chromium.org2013-09-303-3/+5
| | | | | | | | | | | Landed previously in r225857, which was reverted in r225859 because it broke android tests. BUG=103304 R=ben@chromium.org Review URL: https://codereview.chromium.org/25015003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225909 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 225857 "gfx: Create a separate gfx component out of ui."ckocagil@chromium.org2013-09-283-5/+3
| | | | | | | | | | | | | | | > gfx: Create a separate gfx component out of ui. > > BUG=103304 > R=ben@chromium.org > > Review URL: https://codereview.chromium.org/25015003 TBR=sadrul@chromium.org Review URL: https://codereview.chromium.org/25161002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225859 0039d316-1c4b-4281-b951-d872f2087c98
* gfx: Create a separate gfx component out of ui.sadrul@chromium.org2013-09-283-3/+5
| | | | | | | | | BUG=103304 R=ben@chromium.org Review URL: https://codereview.chromium.org/25015003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225857 0039d316-1c4b-4281-b951-d872f2087c98
* Make *CommandBufferProxy* implement GpuControlpiman@chromium.org2013-09-2710-2/+30
| | | | | | | | | | | | | | | | | GpuControl is where we will pipe out-of-band stuff, that is currently done in each of the WGC3D implementations, but we want to move down into GLES2Implementation. This is essentially just a refactoring, since the current GpuControl only deals with GpuMemoryBuffer that's not available out-of-process, but we can then add things like GenerateMailboxes, Ensure/DiscardBackbuffer or callback stuff on top. BUG=181120 R=dmichael@chromium.org, sievers@chromium.org Review URL: https://codereview.chromium.org/24711002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225627 0039d316-1c4b-4281-b951-d872f2087c98
* [Android] set the mapped_memory_limit for the browser compositor. This ↵kaanb@chromium.org2013-09-261-1/+1
| | | | | | | | | | ensures we use smaller shared memory chunks when we upload resources. BUG=297844 Review URL: https://codereview.chromium.org/24685002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225562 0039d316-1c4b-4281-b951-d872f2087c98
* Reenabled ANGLE_instanced_arrays on Windowsbajones@chromium.org2013-09-261-12/+1
| | | | | | | | | | Corruption that was occuring has been fixed in https://code.google.com/p/angleproject/issues/detail?id=467, which has been rolled into Chrome. BUG=288391 Review URL: https://codereview.chromium.org/24672002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225551 0039d316-1c4b-4281-b951-d872f2087c98
* Remove ipc::CommandBufferProxy. As an interface, it's not used.piman@chromium.org2013-09-263-55/+0
| | | | | | | | BUG=None Review URL: https://codereview.chromium.org/24483008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225501 0039d316-1c4b-4281-b951-d872f2087c98
* Allow rendering from non-stream GL_TEXTURE_EXTERNAL_OESsheu@chromium.org2013-09-264-50/+75
| | | | | | | | | | | | Towards support for compositing from GL_TEXTURE_EXTERNAL_OES textures exported by other drivers into the GL stack. BUG=167417 TEST=local build, unittests, run on CrOS snow Review URL: https://codereview.chromium.org/24152009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225410 0039d316-1c4b-4281-b951-d872f2087c98
* Re-enable framebuffer discarding on new ARM driversskyostil@chromium.org2013-09-261-3/+7
| | | | | | | | | | | Re-enable framebuffer discarding on new ARM drivers now that the flickering bug has been fixed. BUG=290876 Review URL: https://codereview.chromium.org/24169007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225306 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up remaining unused globals (on mac).thakis@chromium.org2013-09-262-4/+0
| | | | | | | | | | | | Found by clang's new -Wunused-const-variable. BUG=290204 R=akalin@chromium.org, jamesr@chromium.org, koz@chromium.org, piman@chromium.org, sergeyu@chromium.org, thestig@chromium.org, vitalybuka@chromium.org TBR=cpu, dmichael, joi, xhwang Review URL: https://codereview.chromium.org/24579003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225281 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up a few more unused globals.thakis@chromium.org2013-09-251-3/+4
| | | | | | | | | | | Found by clang's new -Wunused-const-variable. BUG=290204 R=akalin@chromium.org, avi@chromium.org, isherman@chromium.org, jamesr@chromium.org, joi@chromium.org, sergeyu@chromium.org, sky@chromium.org, thestig@chromium.org, xhwang@chromium.org Review URL: https://codereview.chromium.org/24649002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225273 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: [Android] Use 1MB as the MappedMemoryManager chunk size instead of 2MB ↵kaanb@chromium.org2013-09-251-1/+7
| | | | | | | | | | | | | | for low-end devices. Landing with notry since this change only affects Android and Android trybots are green. NOTRY=true BUG=297844 Review URL: https://chromiumcodereview.appspot.com/24445002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@225204 0039d316-1c4b-4281-b951-d872f2087c98
* Enable virtual contexts for all ARM T-6xx models instead of just T-604skyostil@chromium.org2013-09-241-5/+5
| | | | | | | | BUG=294779,282479 Review URL: https://chromiumcodereview.appspot.com/24051003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224977 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 224810 "Enable GPU control lists in tests."piman@chromium.org2013-09-243-44/+3
| | | | | | | | | | | | | | | | | | | | | | | | AcceleratedCompositingBlockedTest.AcceleratedCompositingBlocked fails repeatedly on Mac ASAN: http://build.chromium.org/p/chromium.memory/builders/Mac%20ASAN%20Tests%20%281%29/builds/14941/steps/browser_tests/logs/stdio Also, it may be related to the OutOfProcessPPAPITest.Graphics3D failure: http://build.chromium.org/p/chromium.win/builders/Vista%20Tests%20%281%29/builds/40687/steps/browser_tests/logs/stdio > Enable GPU control lists in tests. > > Reland of https://codereview.chromium.org/23534006/ (see that and the bug for more details). > > Also adding INFO-level logging to spell out each control list rule being applied on the bots (makes debugging and understanding failures much easier). > > R=piman@chromium.org > TBR=jcivelli, piman, zmo > BUG=295799 > > Review URL: https://codereview.chromium.org/23703017 TBR=gab@chromium.org Review URL: https://codereview.chromium.org/24165007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224845 0039d316-1c4b-4281-b951-d872f2087c98
* Enable GPU control lists in tests.gab@chromium.org2013-09-233-3/+44
| | | | | | | | | | | | | | Reland of https://codereview.chromium.org/23534006/ (see that and the bug for more details). Also adding INFO-level logging to spell out each control list rule being applied on the bots (makes debugging and understanding failures much easier). R=piman@chromium.org TBR=jcivelli, piman, zmo BUG=295799 Review URL: https://codereview.chromium.org/23703017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224810 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Upgrade DEPTH_COMPONENT16 to DEPTH_COMPONENT24 if possibleskyostil@chromium.org2013-09-208-49/+92
| | | | | | | | | | | | | | | | | | | Upgrade the DEPTH_COMPONENT16 render buffer storage format to DEPTH_COMPONENT24 if the GLES implementation supports the OES_depth24 extension. This is done to improve content portability between desktop and mobile, since we already do a similar mapping from DEPTH_COMPONENT16 to the unsized DEPTH_COMPONENT on desktop GL. This means that for example WebGL content can end up relying on a higher precision depth buffer even though it only requested DEPTH_COMPONENT16. BUG=285400 TEST=http://www.khronos.org/registry/webgl/conformance-suites/1.0.1/webgl-conformance-tests.html on Nexus 4 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=224117 Review URL: https://chromiumcodereview.appspot.com/24079010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224509 0039d316-1c4b-4281-b951-d872f2087c98
* Disable GL_EXT_discard_framebuffer on older IMG driverssievers@chromium.org2013-09-201-1/+20
| | | | | | | | | BUG=295034 NOTRY=True Review URL: https://chromiumcodereview.appspot.com/23817007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224454 0039d316-1c4b-4281-b951-d872f2087c98
* Expose real VENDOR/RENDERER strings for WEBGL_debug_renderer_info.zmo@chromium.org2013-09-201-6/+5
| | | | | | | | | | | | | Currently we always return "chromium" for both, which is against the purpose of this extension. BUG=294922 TEST=manual R=bajones@chromium.org, kbr@chromium.org Review URL: https://codereview.chromium.org/24244006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224405 0039d316-1c4b-4281-b951-d872f2087c98
* Update accelerated video decode on certain Intel GPUsvangelis@chromium.org2013-09-201-1/+18
| | | | | | | | | | | | It has been observed that accelerated video decode on drivers in the range 8.15.10.1883 to 8.15.10.2702 doesn't work from within the gpu process sandbox. BUG=180695 Review URL: https://chromiumcodereview.appspot.com/23531057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224332 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 224117 "gpu: Upgrade DEPTH_COMPONENT16 to DEPTH_COMPONENT..."thakis@chromium.org2013-09-198-88/+49
| | | | | | | | | | | | | | | | | | | | | | | | | Caused http://crbug.com/294937 > gpu: Upgrade DEPTH_COMPONENT16 to DEPTH_COMPONENT24 if possible > > Upgrade the DEPTH_COMPONENT16 render buffer storage format to > DEPTH_COMPONENT24 if the GLES implementation supports the OES_depth24 > extension. This is done to improve content portability between desktop > and mobile, since we already do a similar mapping from DEPTH_COMPONENT16 > to the unsized DEPTH_COMPONENT on desktop GL. This means that for > example WebGL content can end up relying on a higher precision depth > buffer even though it only requested DEPTH_COMPONENT16. > > BUG=285400 > TEST=http://www.khronos.org/registry/webgl/conformance-suites/1.0.1/webgl-conformance-tests.html on Nexus 4 > > Review URL: https://chromiumcodereview.appspot.com/24079010 TBR=skyostil@chromium.org Review URL: https://codereview.chromium.org/23672048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224166 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Upgrade DEPTH_COMPONENT16 to DEPTH_COMPONENT24 if possibleskyostil@chromium.org2013-09-198-49/+88
| | | | | | | | | | | | | | | | | Upgrade the DEPTH_COMPONENT16 render buffer storage format to DEPTH_COMPONENT24 if the GLES implementation supports the OES_depth24 extension. This is done to improve content portability between desktop and mobile, since we already do a similar mapping from DEPTH_COMPONENT16 to the unsized DEPTH_COMPONENT on desktop GL. This means that for example WebGL content can end up relying on a higher precision depth buffer even though it only requested DEPTH_COMPONENT16. BUG=285400 TEST=http://www.khronos.org/registry/webgl/conformance-suites/1.0.1/webgl-conformance-tests.html on Nexus 4 Review URL: https://chromiumcodereview.appspot.com/24079010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224117 0039d316-1c4b-4281-b951-d872f2087c98
* No longer tolerate unknown fields in gpu blacklist.zmo@chromium.org2013-09-197-80/+13
| | | | | | | | | | | | | Originally we update blacklist independent of chrome update, so a new feature might be added to blacklist, but the old version of chrome may not recognize it. We don't want the total blacklist to fail. Now we no longer have live updates, so we should make sure all the info in the blacklist is valid. BUG= TEST=gpu_unittests Review URL: https://chromiumcodereview.appspot.com/24242002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224078 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Reland r233830. "Adding support for RGBA_4444 tile textures". r223830 ↵kaanb@chromium.org2013-09-191-1/+5
| | | | | | | | | | had a bug in async_pixel_transfer_manager_egl.cc that wasn't directly related to the 4444 support. This patch includes the rest of the files in r223830. Changes to async_pixel_transfer_manager_egl.cc have been moved to the separate patch after fixing the bug: https://codereview.chromium.org/23533067/ BUG=272539 Review URL: https://chromiumcodereview.appspot.com/23447048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224040 0039d316-1c4b-4281-b951-d872f2087c98
* Removing the IsMailboxNameValid check in MailboxManager::ConsumeTexture for ↵jiayl@chromium.org2013-09-191-3/+1
| | | | | | | | | | | | perf. According to piman, the check is unnecessary as the mailbox is already in a map. BUG= Review URL: https://chromiumcodereview.appspot.com/23619079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224017 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Remove DCHECKs in AsyncPixelTransferManagerEGL about egl_image_ not ↵kaanb@chromium.org2013-09-191-3/+8
| | | | | | | | | | being EGL_NO_IMAGE_KHR as with the upcoming 4444 texture support that assumption will no longer hold. BUG=272539 Review URL: https://chromiumcodereview.appspot.com/23533067 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@224001 0039d316-1c4b-4281-b951-d872f2087c98
* Clean up gpu control list json files.zmo@chromium.org2013-09-187-295/+166
| | | | | | | | | | | | | | | | | | | | | | a) always use "value" instead of some places "value" and other places "number". This will simplify a bunch of code duplications in the file processing - but in a separate CL. b) Move duplicate readme out of the json files and create a separate readme format file, and all the json files will just reference this format file. More cleanup will follow this. There should be no behavioral changes from this CL. BUG= TEST=tree R=kbr@chromium.org Review URL: https://codereview.chromium.org/23654048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223935 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Adding support for RGBA_4444 tile textures"tomhudson@google.com2013-09-182-13/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 8e6d15826280b9f11a28060b5b2d2bbef17d15bc (r223830; http://crrev.com/21159007). Although the 4444 textures work on S4, they break on N7v2 and N10. (We've got inconsistent reports about N4.) Passing --disable-4444-textures isn't sufficient to fix the problems. ilevy@ points out that the commit bot is using GN, so could easily have missed this breakage. We're hoping to switch to N4, but in this case there's no guarantee that that would have caught it either. Perhaps the main patch can be landed in pieces next time? From N7: E/chromium(32513): [ERROR:gles2_cmd_decoder.cc(5770)] [.RenderCompositor-0x783c9880]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering or is not 'texture complete' From N10: I/chromium( 2104): [INFO:CONSOLE(0)] "[.WebGLRenderingContext]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering or is not 'texture complete'", source: file:///sdcard/clanktemp/index.html (0) R=skyostil@chromium.org TBR=kaanb@chromium.org BUG=245774,272539 Review URL: https://codereview.chromium.org/24219002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223871 0039d316-1c4b-4281-b951-d872f2087c98
* Adding support for RGBA_4444 tile textureskaanb@chromium.org2013-09-182-4/+13
| | | | | | | | BUG=245774,272539 Review URL: https://chromiumcodereview.appspot.com/21159007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223830 0039d316-1c4b-4281-b951-d872f2087c98
* Add an enable D3D11 flag and blacklist specific intel drivers and windows ↵geofflang@chromium.org2013-09-171-3/+23
| | | | | | | | | | vista from using D3D11. BUG=256863 Review URL: https://chromiumcodereview.appspot.com/24120004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223716 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 223397 "Enable GPU blacklist in tests."nasko@chromium.org2013-09-163-36/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > Enable GPU blacklist in tests. > > Partial re-land of https://codereview.chromium.org/22198004/) -- Always enable FCM on Windows -- Part 1/3. > > On top of fixing some of the issues there; only lands the part that enables the GPU blacklist in tests as the former CL is too hard to land all at once. > > Also keeping --skip-gpu-data-loading around for now to be able to deal with failures caused in layout_tests by this on their own later (this needs to land ASAP and layout_tests don't need this ASAP). > > Another CL will follow to always enable FCM on non-blacklisted Windows machines. > > This part re-enables loading the blacklist in tests (and adds a content_browsertest to make sure that the configuration we expect to be testing is indeed the one we are testing -- this uncertainty is basically the only reason the blacklist was explicitly disabled before). > > This CL also cleans up compositor_util.cc which was enforcing the blacklist twice. > > The original plan was to do this only for Windows as Mac/Linux was causing trouble, but it turns out to be harder to do it only on Windows; so taking care of http://crbug.com/277242 in this CL too after all... > > BUG=233830, 267038, 190942, 277242 > TBR=jcivelli, piman > > Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=219132 > Then Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=219159 > > Then re-committed (part 1/3): https://src.chromium.org/viewvc/chrome?view=rev&revision=221114 > Reverted in: https://src.chromium.org/viewvc/chrome?view=rev&revision=221145 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222105 > > Review URL: https://chromiumcodereview.appspot.com/23534006 TBR=gab@chromium.org Review URL: https://codereview.chromium.org/24074005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223456 0039d316-1c4b-4281-b951-d872f2087c98
* Enable GPU blacklist in tests.gab@chromium.org2013-09-163-4/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Partial re-land of https://codereview.chromium.org/22198004/) -- Always enable FCM on Windows -- Part 1/3. On top of fixing some of the issues there; only lands the part that enables the GPU blacklist in tests as the former CL is too hard to land all at once. Also keeping --skip-gpu-data-loading around for now to be able to deal with failures caused in layout_tests by this on their own later (this needs to land ASAP and layout_tests don't need this ASAP). Another CL will follow to always enable FCM on non-blacklisted Windows machines. This part re-enables loading the blacklist in tests (and adds a content_browsertest to make sure that the configuration we expect to be testing is indeed the one we are testing -- this uncertainty is basically the only reason the blacklist was explicitly disabled before). This CL also cleans up compositor_util.cc which was enforcing the blacklist twice. The original plan was to do this only for Windows as Mac/Linux was causing trouble, but it turns out to be harder to do it only on Windows; so taking care of http://crbug.com/277242 in this CL too after all... BUG=233830, 267038, 190942, 277242 TBR=jcivelli, piman Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=219132 Then Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=219159 Then re-committed (part 1/3): https://src.chromium.org/viewvc/chrome?view=rev&revision=221114 Reverted in: https://src.chromium.org/viewvc/chrome?view=rev&revision=221145 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=222105 Review URL: https://chromiumcodereview.appspot.com/23534006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223397 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Disable EXT_discard_framebuffer on ARM GPUs and expose it for pre-ES3skyostil@chromium.org2013-09-163-2/+20
| | | | | | | | | | | | | | | | Disable the EXT_discard_framebuffer extension on ARM GPUs (e.g., Nexus 10) as it is causing dropped frames and flickering. This patch also exposes the EXT_discard_framebuffer extension on pre-OpenGL ES 3.0 drivers which support it. Tested on Nexus 10, Nexus 4 and Galaxy S4. BUG=290876 Review URL: https://chromiumcodereview.appspot.com/23629043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223338 0039d316-1c4b-4281-b951-d872f2087c98
* Moved multisample buffer verification to the command bufferbajones@chromium.org2013-09-133-2/+146
| | | | | | | | BUG=290391 Review URL: https://chromiumcodereview.appspot.com/23876018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223154 0039d316-1c4b-4281-b951-d872f2087c98
* Adding sievers@ as OWNER in gpu/ and content/common/gpu/piman@chromium.org2013-09-121-0/+1
| | | | | | | | | BUG=None R=sievers@chromium.org Review URL: https://codereview.chromium.org/23783010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222867 0039d316-1c4b-4281-b951-d872f2087c98
* Deprecate restore_scissor_on_fbo_change workaroundsievers@chromium.org2013-09-121-2/+7
| | | | | | | | | | | | | This one was painful on Android and we kept experimentally hammering on it until no corruption remained. It actually incurs a glFlush() on every FBO modification in its current form. It's been fixed, let's get rid of it. NOTRY=True Review URL: https://chromiumcodereview.appspot.com/23441057 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222849 0039d316-1c4b-4281-b951-d872f2087c98
* Remove delete_instead_of_resize_fbo workaroundsievers@chromium.org2013-09-122-5/+2
| | | | | | | | | | | It was only looked at in TextureImageTransportSurface which is not used on Android anymore (well it's instantiated but not resized). NOTRY=True Review URL: https://chromiumcodereview.appspot.com/23684054 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222837 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Record GL state to traceskyostil@chromium.org2013-09-124-0/+193
| | | | | | | | | | | | | | | | This patch adds a GL state tracer for recording information about the context state as trace event objects. This initial version only records a screenshot of the framebuffer contents at every SwapBuffers. Note that because the saving this information can be expensive, the new trace events are added under the "disabled-by-default-gpu.debug" category. BUG=284402 Review URL: https://chromiumcodereview.appspot.com/23926013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222812 0039d316-1c4b-4281-b951-d872f2087c98
* gpu: Re-enable virtual contexts on Qualcommskyostil@chromium.org2013-09-121-1/+16
| | | | | | | | | | | Non-virtual contexts on Qualcomm GPUs sometimes cause out-of-order frames to be displayed, so turn GL context virtualization back on. BUG=289461 Review URL: https://chromiumcodereview.appspot.com/23460029 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222769 0039d316-1c4b-4281-b951-d872f2087c98
* Build fix: add a dummy file for gles2_conform_test_windowless targetzmo@chromium.org2013-09-111-0/+7
| | | | | | | | | | TEST=gpu bots TBR=thakis@chromium.org BUG= Review URL: https://codereview.chromium.org/23606028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222611 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Invalidate appropriate FBO attachment for offscreen renderingskyostil@chromium.org2013-09-111-1/+26
| | | | | | | | | | | | | | | | The glInvalidateFramebuffer() uses different attachment names for the default framebuffer and offscreen framebuffers. In the first case we should use GL_COLOR_EXT, whereas offscreen framebuffers expect GL_COLOR_ATTACHMENTn. This patch adds code to keep track of whether GLRenderer is drawing to the default framebuffer or an offscreen one. This information is used to pass the right attachment name when clearing and invalidating the framebuffer. BUG=288635 Review URL: https://chromiumcodereview.appspot.com/24089004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222568 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the problematic call to GLSurface::GetBackingFrameBufferObject.msimonides@opera.com2013-09-111-2/+1
| | | | | | | | | | | | | | | | | | | | | | GLContextVirtual::IsCurrent doesn't need to call GetBackingFrameBufferObject on a surface, the IsOffScreen check should be enough. The direct reason for this change is that GLContextVirtual::IsCurrent's use of GetBackingFrameBufferObject interferes with the implementation of that function in TextureImageTransportSurface. TextureImageTransportSurface::GetBackingFrameBufferObject creates an FBO if needed. Unfortunately GLContextVirtual::IsCurrent is called early in GLContextVirtual's initialization, too early for TextureImageTransportSurface::GetBackingFrameBufferObject to create the frame buffer object because it needs a fully initialized context to succeed. BUG= Review URL: https://chromiumcodereview.appspot.com/23480048 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222505 0039d316-1c4b-4281-b951-d872f2087c98
* Roll in ANGLE and turn on gl_Position init workaround.zmo@chromium.org2013-09-091-3/+2
| | | | | | | | | BUG=286468 TEST=tree Review URL: https://chromiumcodereview.appspot.com/23513025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222134 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 222105 "Enable GPU blacklist in tests."rouslan@chromium.org2013-09-093-36/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Failed on mac-asan bot: http://build.chromium.org/p/chromium.memory/builders/Mac%20ASAN%20Tests%20%281%29/builds/14510 AcceleratedCompositingBlockedTest.AcceleratedCompositingBlocked: [7719:3847:0909/155847:1828989999085:INFO:gpu_control_list.cc(1043)] Control list match for rule #48. [7719:3847:0909/155847:1829419815783:INFO:gpu_control_list.cc(1043)] Control list match for rule #48. [7719:3847:0909/155847:1829591550844:INFO:gpu_control_list.cc(1043)] Control list match for rule #. ../../chrome/test/gpu/gpu_feature_browsertest.cc:143: Failure Value of: 0U Actual: 0 Expected: event_count Which is: 1 > Enable GPU blacklist in tests. > > Partial re-land of https://codereview.chromium.org/22198004/) -- Always enable FCM on Windows -- Part 1/3. > > On top of fixing some of the issues there; only lands the part that enables the GPU blacklist in tests as the former CL is too hard to land all at once. > > Also keeping --skip-gpu-data-loading around for now to be able to deal with failures caused in layout_tests by this on their own later (this needs to land ASAP and layout_tests don't need this ASAP). > > Another CL will follow to always enable FCM on non-blacklisted Windows machines. > > This part re-enables loading the blacklist in tests (and adds a content_browsertest to make sure that the configuration we expect to be testing is indeed the one we are testing -- this uncertainty is basically the only reason the blacklist was explicitly disabled before). > > This CL also cleans up compositor_util.cc which was enforcing the blacklist twice. > > The original plan was to do this only for Windows as Mac/Linux was causing trouble, but it turns out to be harder to do it only on Windows; so taking care of http://crbug.com/277242 in this CL too after all... > > BUG=233830, 267038, 190942, 277242 > TBR=jcivelli, piman > > Originally Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=219132 > Then Reverted: https://src.chromium.org/viewvc/chrome?view=rev&revision=219159 > > Then re-committed (part 1/3): https://src.chromium.org/viewvc/chrome?view=rev&revision=221114 > Reverted in: https://src.chromium.org/viewvc/chrome?view=rev&revision=221145 > > Review URL: https://chromiumcodereview.appspot.com/23534006 TBR=gab@chromium.org Review URL: https://codereview.chromium.org/23983019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@222129 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-01-30 05:35:33 +0000