Hi I have (allmost) DFB running on an embedded ARM 9 CPU, and even though my framebuffer do work (have tried simple non DFB framebuffer examples). Then DFB reports "unsupported destination format". It seems to be because my virtual Y-res is 0, even though the real Y-resolution is 480.
I suppose it's the linux framebuffer driver which reports this and perhaps does not support virtual resolutions...? Maybe I can fix the linux-driver as I do have the code, but since the video memory is in main RAM anyway I would guess that from a performance view it's just as good to force DFB to use sys-mem for backbuffer (disable backbuffer). Is a non zero virtual Y-res stricyly necessary ? allways or can I perhaps circumvent this demand by writing my own DFB driver ? My linux kernel on the device is 2.21 ... don't know if that's a problem .. ? I have tried to force backbuffer to system memory by setting the appropriate option in 'directfbrc' but it seems that it gets 'overruled' later by some other code that the config read stuff. Right now I would just liek to see some output on the screen, then I can later try to write a real DFB display driver. -Regards Martin L�tken _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
