Sorry I misread your suggestion. I now pass NULL as second argument to fbScreenInit(). Driver seems to work fine on non-Xv stuff so that seems fine.
I'm not so sure the current issue is still with the pixmap being pinned nor that it is the screen pixmap. The fb_ptr on the pixmap is still NULL, the sys_ptr isn't, so I guess the pixmap is offscreen and I need to move/force it onscreen somehow ? exaMoveInPixmap() doesn't work since that one skips its functionality if EXA_OFFSCREEN_PIXMAPS is set (and it needs to be set otherwise there is a crash in libexa.so ...) Also to note, sys_ptr=0xb6c1c000 and memoryBase=0xb4a74000. Any Idea how I can access the framebuffer address of the pixmap from within the driver? -Yves On Fri, 2010-07-23 at 12:57 +0200, Michel Dänzer wrote: > On Fre, 2010-07-23 at 12:07 +0200, Yves De Muyter wrote: > > Second argument of fbScreenInit() is definitely not NULL but points to > > the framebuffer address like it should. > > Again, you need to pass NULL to prevent the screen pixmap from being > pinned in system memory. > > > -- > Earthling Michel Dänzer | http://www.vmware.com > Libre software enthusiast | Debian, X and DRI developer > _______________________________________________ > [email protected]: X.Org support > Archives: http://lists.freedesktop.org/archives/xorg > Info: http://lists.freedesktop.org/mailman/listinfo/xorg > Your subscription address: [email protected] _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: [email protected]
