drm/nouveau/gpuobj: remove flags for vm-mappings
Having GPUOBJ and VM intertwined like this makes it *really* hard to
continue porting to the new driver architecture, split it out in
favour of requiring explit maps be the caller.
It's more flexible and obvious this way anyway...
Signed-off-by:
Ben Skeggs <bskeggs@redhat.com>
Showing
- drivers/gpu/drm/nouveau/core/engine/copy/nvc0.c 25 additions, 11 deletionsdrivers/gpu/drm/nouveau/core/engine/copy/nvc0.c
- drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c 50 additions, 21 deletionsdrivers/gpu/drm/nouveau/core/engine/graph/nvc0.c
- drivers/gpu/drm/nouveau/core/engine/graph/nvc0.h 5 additions, 0 deletionsdrivers/gpu/drm/nouveau/core/engine/graph/nvc0.h
- drivers/gpu/drm/nouveau/core/engine/graph/nve0.c 50 additions, 20 deletionsdrivers/gpu/drm/nouveau/core/engine/graph/nve0.c
- drivers/gpu/drm/nouveau/core/engine/graph/nve0.h 5 additions, 0 deletionsdrivers/gpu/drm/nouveau/core/engine/graph/nve0.h
- drivers/gpu/drm/nouveau/core/subdev/instmem/nv50.c 0 additions, 18 deletionsdrivers/gpu/drm/nouveau/core/subdev/instmem/nv50.c
- drivers/gpu/drm/nouveau/nouveau_drv.h 0 additions, 3 deletionsdrivers/gpu/drm/nouveau/nouveau_drv.h
- drivers/gpu/drm/nouveau/nouveau_gpuobj.c 1 addition, 1 deletiondrivers/gpu/drm/nouveau/nouveau_gpuobj.c
Loading
Please register or sign in to comment