diff options
| author | marcheu <marcheu@chromium.org> | 2016-02-24 19:20:48 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-25 03:22:22 +0000 |
| commit | 1462a929e00255654a06d3e905adc72ba1255ad5 (patch) | |
| tree | 0288d07330b6067b40d02f2c52fd73a0fff01164 /extensions/renderer | |
| parent | 04b75d3ac2b44bfefa7409e8a36c87c2144069f1 (diff) | |
| download | chromium_src-1462a929e00255654a06d3e905adc72ba1255ad5.zip chromium_src-1462a929e00255654a06d3e905adc72ba1255ad5.tar.gz chromium_src-1462a929e00255654a06d3e905adc72ba1255ad5.tar.bz2 | |
Ozone: Remove misleading comment about tiling
The GBM_BO_USE_SCANOUT flag isn't a hint to set tiling, and especially
not a platform-specific tiling format. It is a flag to specify that we
are going to use that buffer as a scanout.
As a side node, Chrome currently (incorrectly) assumes that not
setting any flag results in a linear buffer. We should probably add a
new flag like GBM_BO_USE_LINEAR to support this as there is no
guarantee of linearity otherwise.
BUG=none
TEST=builds
Review URL: https://codereview.chromium.org/1733123002
Cr-Commit-Position: refs/heads/master@{#377484}
Diffstat (limited to 'extensions/renderer')
0 files changed, 0 insertions, 0 deletions