{"push_id":960948903,"size":21,"distinct_size":21,"ref":"refs/heads/v48","head":"148abde5cc46ecb5553e3d425e42c8d70db4eca2","before":"b01570933031c5fd0f4d01f623d4a61a1d79a008","commits":[{"sha":"5c79f950456689f167989df6f7f87ebf7ed7b23d","author":{"email":"b3c7ac1f4c4c45c9f838c275805c43367661d6f7@endlessm.com","name":"Daniel Drake"},"message":"Enable V4L2 accelerated video decoding on Linux/ARM","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/5c79f950456689f167989df6f7f87ebf7ed7b23d"},{"sha":"2473e3cd4721d055cbd3e3d63a7793ba8e7c8260","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: check new M2M capability flags\n\nThis check was out of date.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/2473e3cd4721d055cbd3e3d63a7793ba8e7c8260"},{"sha":"cc8a3ae288f0d696e4757a37ba1588f884d2b3e6","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: Export dmabufs as read-only","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/cc8a3ae288f0d696e4757a37ba1588f884d2b3e6"},{"sha":"b6672452bd21bf10fa717ded38c5097b614a8744","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: Disable V4L2_CID_MIN_BUFFERS_FOR_CAPTURE checks\n\nmeson-vdec doesn't support this at the moment.\nWe might implement it later.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/b6672452bd21bf10fa717ded38c5097b614a8744"},{"sha":"72195a89bc9a710f95de3d04df55060e0d37ae16","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: reduce number of input buffers\n\nThis improves memory usage.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/72195a89bc9a710f95de3d04df55060e0d37ae16"},{"sha":"ed27b9641dd45612314d6fe5b473786dac25f7b5","author":{"email":"b3c7ac1f4c4c45c9f838c275805c43367661d6f7@endlessm.com","name":"Daniel Drake"},"message":"v4l2: set color space and sample range hints\n\nMali's NV12 dmabuf import code requires these.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/ed27b9641dd45612314d6fe5b473786dac25f7b5"},{"sha":"548caa93b7fded90e89bd91bb66832d4c2c114c6","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"gpu_video_decoder: Properly track buffer data\n\nRing buffer based decoder may accumulate way more then 127 buffers in\ncase of very small size videos. Instead of randomly poping out buffer\ndata, properly track input and output and remove when buffer are\ndecoded.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/548caa93b7fded90e89bd91bb66832d4c2c114c6"},{"sha":"30593134856427c3fe1d7cc19a5113a5c4148169","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: Use empty payload buffer to detect end of drain\n\nThe drain path is bogus. It assumes that the decoder have no\ninternal queue and that the input buffer are returned only\nwhen they are decoded. This does not work for decoder with a\nring buffer.\n\nInstead, simply wait for the empty payload buffer. This prevent\nflushing the frame data too soon when EOS is reached.","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/30593134856427c3fe1d7cc19a5113a5c4148169"},{"sha":"9cd92499f721e4e88fc16676f7ef71d2fe125d1f","author":{"email":"b3c7ac1f4c4c45c9f838c275805c43367661d6f7@endlessm.com","name":"Daniel Drake"},"message":"v4l2: create EGL image with true row stride\n\nWhen creating EGL Images from video frames, Chromium was always using\na calculation based on the display width as the image buffer stride.\nThat was resulting in some videos being played back slanted (wrong\nstride), and other EGL image imports being rejected by Mali due to not\nmeeting basic alignment requirements.\n\nTake the stride info from V4L2 and use it in the EGLCreateImage call\nto solve this.\n\n[endlessm/eos-shell#5464]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/9cd92499f721e4e88fc16676f7ef71d2fe125d1f"},{"sha":"b59008655f8c38c7c1a177e0aa127aa286140f92","author":{"email":"36c35e0aac84fcb59b447cc6415df42e7fda8df7@collabora.com","name":"Nicolas Dufresne"},"message":"v4l2: Increase number of output buffers\n\nThis has been increased using trial and error. When this number is to\nlow, we can notice video being slower then real time. After a certain\namount of dsync, chrome will skip to next key frame to catchup. That is\nmainly because of the rendering being slower then real time. Combined\nwith low number of output buffers, the decoder is being slowed down, at\nwhich point frames are all late.\n\nThis work for all 1080p@30fps and 720p@60pfs I have could find on\nYoutube. Note that 1080p@60fps is still problematic. At which point, I\ncan only assume that the decoder is two slow (or at least the\ncombination of the decoder and the ge2d is to slow).\n\n[endlessm/eos-shell/issues/5991]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/b59008655f8c38c7c1a177e0aa127aa286140f92"},{"sha":"e08696a9b6119498c715632022504bfedbcca198","author":{"email":"b3c7ac1f4c4c45c9f838c275805c43367661d6f7@endlessm.com","name":"Daniel Drake"},"message":"DecoderSelector: prefer DecryptingDemuxerStream on ARM\n\nThe default choice of DecryptingDecoderType appears to do\nencrypted content decrypting and decoding in the CDM module.\n\nIn order to use the hardware accelerated video decoding, on ARM,\ninstead prefer DecryptingDemuxerStream, so that the CDM module\nonly decrypts the content, leaving decoding to the normal codepaths.\n\n[endlessm/eos-shell#5850]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/e08696a9b6119498c715632022504bfedbcca198"},{"sha":"888576e585c948a059610e7395d62f845379b5e3","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Don't ever play the default \"First Run experience\"\n\nWe don't want to ever show the bubble overlay popping out of the address\nbar on the first run, nor the Getting Started webpage on a second tab.\n\nThis change has the problem that it invalidates the master_preferences\nfeature, as those get imported only during the first run, but it should\nbe fine as we are not using that now (nor planning to use it in the near\nfuture) and that is a feature already on its way to being deprecated.\n\n[endlessm/eos-shell#5937]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/888576e585c948a059610e7395d62f845379b5e3"},{"sha":"75ff3aefddf5f3d8a368a5d6d22e758f29dec168","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"desktop_aura: Use a white pixel to fill the XWindow's background\n\nInstead of using nothing, which causes some weird effects when launching\nchromium (e.g. XWindow initialized with data from the front buffer), while\nthe first expose event is not attended, define instead a solid colour\nfor the background so that at least the startup experience is consistent.\n\n[endlessm/eos-shell#5873]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/75ff3aefddf5f3d8a368a5d6d22e758f29dec168"},{"sha":"37c6d82323238d24c89272ffacb2b216799a4ed4","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@mariospr.org","name":"Mario Sanchez Prada"},"message":"desktop_aura: Unset XWindow's background once it's mapped\n\nIn commit 8d8fb734, we set the XWindow's background pixel to white to\nmake the flickering during startup less annoying, but that had the side\neffect of making resizing quite disturbing, since the background is\nquite visible while resizing, due to the slow rendering process.\n\nThis patch makes sure that the XWindow's background is unset (set to\nNone) once the window has been Mapped, thus making the resizing\nexperience as \"good\" as it used to be prior to that change.\n\n[endlessm/eos-shell#5873]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/37c6d82323238d24c89272ffacb2b216799a4ed4"},{"sha":"fbd2a49fbd452c3718a5c346f45013270fd81e8e","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Wait until the first SwapBuffers before resetting XWindow's background pixmap\n\nThis is a temporary solution while we work on fixing the issue upstream\nin proper way, since the current experience on ARM is pretty bad, with\npart of the screen being filled in white and the rest on black on startup.\n\nSee also: https://code.google.com/p/chromium/issues/detail?id=554008\n\n[endlessm/eos-shell#6068]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/fbd2a49fbd452c3718a5c346f45013270fd81e8e"},{"sha":"197481f4c9ccaaf0105a34c000ac4afc528ab7db","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Use our own icons for buttons in Chromium's titlebar\n\nThis should mean a more consistent UI when not using system titlebars.\n\n[endlessm/eos-shell#5857]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/197481f4c9ccaaf0105a34c000ac4afc528ab7db"},{"sha":"e03773da48d6a18c173e63b388b3375a3f21f70e","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Use Chromium titlebars on ARM\n\nWhen system title bars are used, Chromium renders onto one window pixmap,\nand each frame is then then copied into a slightly larger one including\nthe window manager's window decorations.\n\nWhen native title bars are used, Chromium renders directly into the\nvisible window pixmap. This provides a significant performance improvement\non ARM where the copy would otherwise be done with the CPU.\n\nOn Intel, there is no noticable performance gain, so we leave system\ntitlebars in place for consistency with the rest of the desktop.\n\n[endlessm/eos-shell#5184]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/e03773da48d6a18c173e63b388b3375a3f21f70e"},{"sha":"8857d91fd606be526ffd5025ea70ef19633e7bec","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Always use buttons from chromium's classic theme, even for GTK+ theme\n\nThe navigation buttons from the GTK+ theme are rendered very blurry and\njagged when running with higher text-scaling-factor values (higher DPI)\nand, on top of that, they look worse in general than the ones from the\nclassic theme, so make sure that we these other ones instead.\n\nNote that other definitions from the GTK+ Theme, as defined via the relevant\ngtkrc file provided for the Adwaita theme, will be still used by chromium\nto render other details of the UI. This change affects the buttons only.\n\n[endlessm/eos-shell#5869]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/8857d91fd606be526ffd5025ea70ef19633e7bec"},{"sha":"96271b575729fc16d4c587fe777a11c7131ae0e9","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Use float instead of double literals when blacklisting low scale factors\n\nOtherwise, the comparison will effectively work as 'rounded < 1.4f'.\n\n[endlessm/eos-shell#6197]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/96271b575729fc16d4c587fe777a11c7131ae0e9"},{"sha":"406f4c13128feb6360f51b9a35db517d770934b4","author":{"email":"addb47291ee169f330801ce73520b96f2eaf20ea@endlessm.com","name":"Mario Sanchez Prada"},"message":"Consider com.endlessm.CompositeMode.text-scaling-factor GSetting if available\n\nIf the eos-composite-mode package is installed, the\ncom.endlessm.CompositeMode will be available to provide an additional,\naccumulative, scaling factor to be used on top of the one from\norg.gnome.desktop.interface, so we need to check it here to determine the\nright value to set for the global Xft DPI setting.\n\nContrary to what gnome-settings-daemon does (check the\n'text-scaling-factor' key from the schema), chromium checks the\n'browser-scaling-factor' key instead, which is defined by\neos-composite-mode to be specifically used by the browser only, so that we\ncan define an additional scaling factor just for it.\n\n[endlessm/eos-shell#6197]","distinct":true,"url":"https://api.github.com/repos/endlessm/chromium-browser/commits/406f4c13128feb6360f51b9a35db517d770934b4"}]}