Den 23.07.2017 21.16, skrev Noralf Trønnes:
This adds defaults for the drm_driver.dumb_destroy and
drm_driver.dumb_map_offset callbacks as discussed with Daniel.
vmwgfx is the only driver that doesn't use drm_gem_dumb_destroy().
vgem
vgem changes behaviour after this, because it didn't ha
On 07/23/2017 09:16 PM, Noralf Trønnes wrote:
> This adds defaults for the drm_driver.dumb_destroy and
> drm_driver.dumb_map_offset callbacks as discussed with Daniel.
>
> vmwgfx is the only driver that doesn't use drm_gem_dumb_destroy().
>
> vgem
>
> vgem changes behaviour after this, bec
On Mon, Jul 24, 2017 at 09:39:08PM +0200, Noralf Trønnes wrote:
>
> Den 23.07.2017 21.16, skrev Noralf Trønnes:
> > This adds defaults for the drm_driver.dumb_destroy and
> > drm_driver.dumb_map_offset callbacks as discussed with Daniel.
> >
> > vmwgfx is the only driver that doesn't use drm_gem_
Den 23.07.2017 21.16, skrev Noralf Trønnes:
This adds defaults for the drm_driver.dumb_destroy and
drm_driver.dumb_map_offset callbacks as discussed with Daniel.
vmwgfx is the only driver that doesn't use drm_gem_dumb_destroy().
vgem
vgem changes behaviour after this, because it didn't ha
This adds defaults for the drm_driver.dumb_destroy and
drm_driver.dumb_map_offset callbacks as discussed with Daniel.
vmwgfx is the only driver that doesn't use drm_gem_dumb_destroy().
vgem
vgem changes behaviour after this, because it didn't have .dumb_destroy
set, something the docs mandat
