I've got a strange problem with DirectFB on a Matrox G450, using TV out.
Sometimes DirectFBCreate fails with this error:
(!) DirectFB/FBDev: Could not mmap MMIO region (offset 0, length 16384)!
--> Invalid argument
(!) DirectFB/Core: Could not initialize 'gfxcard' core!
--> General I/O error!
It happens both in a program called thebox which I'm writing (it's
basically a menu/file browser for MPlayer ATM) and in MPlayer, and it
happens on two different PCs, both with a G450.
This always happens the first time I try one of the offending programs
after booting up. If I rerun thebox or mplayer it always works the
second time, but occasionally when thebox tries to reopen the display
after calling MPlayer it happens again.
Before calling MPlayer thebox releases all its DirectFB resources as far
as releasing the IDirectFB struct, then afterwards resumes by starting
again from DirectFBCreate, but without calling DirectFBInit again. Is
that a reasonable way to do it or would I be better hanging on to all
the DirectFB resources in thebox and just forcing a redraw when it
resumes from MPlayer?
Seeing as the programs always work immediately if run again I thought I
might be able to work around the problem by trying to call
DirectFBCreate again, but it crashes with a segfault. I've also tried
calling DirectFBInit again first (thebox doesn't currently pass any args
to that) and even reloading thebox's DirectFB plugin, because that (I
hoped) should completely clear the DirectFB library too, being the only
part of thebox which is linked with it. But it still segfaults.
--
TH * http://www.realh.co.uk
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
