diff options
| author | Daniel Kurtz <djkurtz@chromium.org> | 2014-04-04 17:22:02 +0800 |
|---|---|---|
| committer | Inki Dae <daeinki@gmail.com> | 2014-06-02 02:07:02 +0900 |
| commit | b90f54188f2d630d826960e33e1ea8e27e43a33f (patch) | |
| tree | 42d163f136f8da79b5ad2c0b4991e1c890609bbc /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | 2f1eab8d8ab59e799f7d51d62410b398607a7bc3 (diff) | |
drm/exynos/fbdev: don't set mode_config.fb_base
AFAICT, the fb_base of a drm_device's mode_config is never used. It isn't
accessed by core drm, it isn't used by fbmem, and it isn't exposed to user
space.
Furthermore, it is probably supposed to be a physical address, not the
dma address mapped to the display controller, so this is just wrong.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Inki Dae <inki.dae@samsung.com>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions