[PATCH] drm: Compare only lower 32 bits of framebuffer map offsets

2011-05-30 Thread Dave Airlie
On Mon, 2011-05-30 at 01:12 +0200, Tormod Volden wrote: > From: Tormod Volden > > Drivers using multiple framebuffers got broken by commit > 41c2e75e60200a860a74b7c84a6375c105e7437f which ignored the framebuffer > (or register) map offset when looking for existing maps. The rationale > was that t

[PATCH] drm: Compare only lower 32 bits of framebuffer map offsets

2011-05-30 Thread Tormod Volden
From: Tormod Volden Drivers using multiple framebuffers got broken by commit 41c2e75e60200a860a74b7c84a6375c105e7437f which ignored the framebuffer (or register) map offset when looking for existing maps. The rationale was that the kernel-userspace ABI is fixed at a 32-bit offset, so the real off

Re: [PATCH] drm: Compare only lower 32 bits of framebuffer map offsets

2011-05-29 Thread Dave Airlie
On Mon, 2011-05-30 at 01:12 +0200, Tormod Volden wrote: > From: Tormod Volden > > Drivers using multiple framebuffers got broken by commit > 41c2e75e60200a860a74b7c84a6375c105e7437f which ignored the framebuffer > (or register) map offset when looking for existing maps. The rationale > was that t

[PATCH] drm: Compare only lower 32 bits of framebuffer map offsets

2011-05-29 Thread Tormod Volden
From: Tormod Volden Drivers using multiple framebuffers got broken by commit 41c2e75e60200a860a74b7c84a6375c105e7437f which ignored the framebuffer (or register) map offset when looking for existing maps. The rationale was that the kernel-userspace ABI is fixed at a 32-bit offset, so the real off