提交 635cb7da 编写于 作者: A Alexandre Courbot 提交者: Ben Skeggs

drm/nouveau/fb/gk20a: fix constructor call

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: NAlexandre Courbot <acourbot@nvidia.com>
Signed-off-by: NBen Skeggs <bskeggs@redhat.com>
上级 ed7acfae
...@@ -20,6 +20,7 @@ ...@@ -20,6 +20,7 @@
* DEALINGS IN THE SOFTWARE. * DEALINGS IN THE SOFTWARE.
*/ */
#include "priv.h" #include "priv.h"
#include "gf100.h"
#include <core/memory.h> #include <core/memory.h>
...@@ -42,5 +43,5 @@ gk20a_fb = { ...@@ -42,5 +43,5 @@ gk20a_fb = {
int int
gk20a_fb_new(struct nvkm_device *device, int index, struct nvkm_fb **pfb) 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);
} }
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册