summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/drm_vm.c
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2010-08-30 21:25:23 +0200
committerChris Wilson <chris@chris-wilson.co.uk>2010-09-06 23:09:52 +0100
commit9f82d23846146990d475f6753be733e55788d88d (patch)
tree9e9763c3c85c3a1e15be7b123ddd63d5a20efaac /drivers/gpu/drm/drm_vm.c
parent300387c0b57d75e5218e2881d6ad2720657a8bcf (diff)
downloadtalos-op-linux-9f82d23846146990d475f6753be733e55788d88d.tar.gz
talos-op-linux-9f82d23846146990d475f6753be733e55788d88d.zip
drm/i915: overlay on gen2 can't address above 1G
So set the coherent dma mask accordingly. This dma mask is only used for physical objects, so it won't really matter allocation-wise. Now this never really surfaced because sane 32bit kernels only have 1G of lowmem. But some eager testers (distros?) still carry around the patch to adjust lowmem via a kconfig option. And the kernel seems to favour high allocations on boot-up, hence the overlay blowing up reliably. Because the patch is tiny and nicely shows how broken gen2 is it's imho worth to merge despite the fact that mucking around with the lowmem/ highmem division is (no longer) supported. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=28318 Cc: stable@kernel.org Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'drivers/gpu/drm/drm_vm.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud