[Intel-gfx] [PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-08-01 Thread Patrik Jakobsson
On Tue, Jul 16, 2013 at 9:12 AM, Daniel Vetter wrote: > All the gem based kms drivers really want the same function to > destroy a dumb framebuffer backing storage object. > > So give it to them and roll it out in all drivers. > > This still leaves the option open for kms drivers which don't use

Re: [Intel-gfx] [PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-08-01 Thread Patrik Jakobsson
On Tue, Jul 16, 2013 at 9:12 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: All the gem based kms drivers really want the same function to destroy a dumb framebuffer backing storage object. So give it to them and roll it out in all drivers. This still leaves the option open for kms drivers

[PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-23 Thread Inki Dae
> -Original Message- > From: Daniel Vetter [mailto:daniel.vetter at ffwll.ch] > Sent: Tuesday, July 16, 2013 4:12 PM > To: DRI Development > Cc: Daniel Vetter; Inki Dae; Laurent Pinchart; Intel Graphics Development; > Ben Skeggs; Rob Clark; Alex Deucher > Subject:

[PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-23 Thread Laurent Pinchart
Hi Daniel, Thanks for the patch. On Tuesday 16 July 2013 09:12:04 Daniel Vetter wrote: > All the gem based kms drivers really want the same function to > destroy a dumb framebuffer backing storage object. > > So give it to them and roll it out in all drivers. > > This still leaves the option

Re: [PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-23 Thread Laurent Pinchart
Hi Daniel, Thanks for the patch. On Tuesday 16 July 2013 09:12:04 Daniel Vetter wrote: All the gem based kms drivers really want the same function to destroy a dumb framebuffer backing storage object. So give it to them and roll it out in all drivers. This still leaves the option open

RE: [PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-23 Thread Inki Dae
-Original Message- From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] Sent: Tuesday, July 16, 2013 4:12 PM To: DRI Development Cc: Daniel Vetter; Inki Dae; Laurent Pinchart; Intel Graphics Development; Ben Skeggs; Rob Clark; Alex Deucher Subject: [PATCH 13/20] drm/gem: create

[PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-22 Thread Rob Clark
On Tue, Jul 16, 2013 at 3:12 AM, Daniel Vetter wrote: > All the gem based kms drivers really want the same function to > destroy a dumb framebuffer backing storage object. > > So give it to them and roll it out in all drivers. > > This still leaves the option open for kms drivers which don't use

Re: [PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-22 Thread Rob Clark
On Tue, Jul 16, 2013 at 3:12 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: All the gem based kms drivers really want the same function to destroy a dumb framebuffer backing storage object. So give it to them and roll it out in all drivers. This still leaves the option open for kms drivers

[PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-16 Thread Daniel Vetter
All the gem based kms drivers really want the same function to destroy a dumb framebuffer backing storage object. So give it to them and roll it out in all drivers. This still leaves the option open for kms drivers which don't use GEM for backing storage, but it does decently simplify matters

[PATCH 13/20] drm/gem: create drm_gem_dumb_destroy

2013-07-16 Thread Daniel Vetter
All the gem based kms drivers really want the same function to destroy a dumb framebuffer backing storage object. So give it to them and roll it out in all drivers. This still leaves the option open for kms drivers which don't use GEM for backing storage, but it does decently simplify matters