Second argument of fbScreenInit() is definitely not NULL but points to the framebuffer address like it should.
I have been debugging some more. It looks like pExaPixmap->fb_ptr is NULL, and in exaGetPixmapOffset() it returns fb_ptr - memoryBase without ever checking fb_ptr resulting in a (0 - memoryBase) offset. Is there a function where I can force it to move the pixmap onto the framebuffer? I tried exaMoveInPixmap but that doesn't result in anything filled in fb_ptr. using exaPrepareAccess(pPixmap->drawable, EXA_PREPARE_DEST) and exaFinishAccess() just crashes xorg... I'd rather not use sys_ptr because that will probably be slow for Xv... -Yves On Fri, 2010-07-23 at 10:33 +0200, Michel Dänzer wrote: > On Don, 2010-07-22 at 20:18 +0200, Yves De Muyter wrote: > > > > I have now ported the driver to exa_mixed (also because the > > exa_classic bugfix is not being backported to 1.7 and this way we > > bypass the issue). > > > > Driver seems to work fine, just like it did under exa_classic. > > > > But the same issue remains, mplayer and others still use the > > fullscreen pixmap as a Xv pixmap and that one is 'pinned'. > > It shouldn't be, make sure you don't pass a non-NULL second argument to > fbScreenInit(). > > > -- > 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]
