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

2011-06-11 Thread Tormod Volden
On Mon, May 30, 2011 at 9:45 PM, 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 the

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

2011-06-10 Thread Tormod Volden
On Mon, May 30, 2011 at 9:45 PM, 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 the

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

2011-06-01 Thread Tormod Volden
On Mon, May 30, 2011 at 9:45 PM, Tormod Volden wrote: > (*) It actually checks if _DRM_CONTAINS_LOCK is the /only/ flag set. I > suppose this is intentional. My v2 patch does not change anything in the > case of _DRM_SHM: If it contains a lock, it returns a match without > comparing offsets. If no

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

2011-05-31 Thread Tormod Volden
On Mon, May 30, 2011 at 9:45 PM, Tormod Volden wrote: > (*) It actually checks if _DRM_CONTAINS_LOCK is the /only/ flag set. I > suppose this is intentional. My v2 patch does not change anything in the > case of _DRM_SHM: If it contains a lock, it returns a match without > comparing offsets. If no

[PATCH v2] 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

[PATCH v2] 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