Hi Jérémy,
that is for me quite tricky to answer without the set-up.
it could be that the fbdev driver incorrectly returns 640x480 as screen
resolution, causing DirectFB to change.
It is also interesting to turn the DirectFB debug statements on - you
should get a print of dfb_fbdev_read_modes() followed by the modes that
were successfully detected. If 800x480 fails, expect a frame buffer
problem; you might get away by hacking hard-coded values in DirectFB.
hth
Niels
Jérémy Morel wrote:
Hi !
Thanks for the answer. I already saw the page but discarded it because
of the necessary Kernel compilation. However, since you said it was
what I had to do, I took a harder look at it, and with some packages
and modprobe, I got it to work. Yay ! Thanks again.
However, when I try simple.c, the example you give in the tutorial
section, with the end of the line set at 640-1, the whole screen is
covered ! It seems like DirectFB reverted the resolution back to
640x480. I tried to add the line SetVideoMode (dfb, 800, 480, 32) but
then I get a segfault, or, if I use the DFBCHECK function, I get
"DirectFBError [dfb->SetVideoMode (dfb, 800, 480, 32) ]: not
supported". However, I can still do a dfb->SetVideoMode (dfb, 640,
480, 32) and it works fine.
Would you know why ?
--
Jérémy
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
