The gf100 constructor should be called, otherwise we will allocate a smaller object than expected. This was without effect so far because gk20a did not allocate a page, but with gf100's page allocation moved to the oneinit() hook this problem has become apparent.
Signed-off-by: Alexandre Courbot <[email protected]> --- drm/nouveau/nvkm/subdev/fb/gk20a.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/subdev/fb/gk20a.c b/drm/nouveau/nvkm/subdev/fb/gk20a.c index f815fe2bbf08..3f516f5adc30 100644 --- a/drm/nouveau/nvkm/subdev/fb/gk20a.c +++ b/drm/nouveau/nvkm/subdev/fb/gk20a.c @@ -20,6 +20,7 @@ * DEALINGS IN THE SOFTWARE. */ #include "priv.h" +#include "gf100.h" #include <core/memory.h> @@ -42,5 +43,5 @@ gk20a_fb = { int gk20a_fb_new(struct nvkm_device *device, int index, struct nvkm_fb **pfb) { - return nvkm_fb_new_(&gk20a_fb, device, index, pfb); + return gf100_fb_new_(&gk20a_fb, device, index, pfb); } -- 2.10.0 _______________________________________________ Nouveau mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/nouveau
