Hi Pier,
not sure what the problem is but can give some hints.
first, RGB16 is RGB 5/6/5 where you seem to have RGB 5/5/5, but that
should in fact make your screen look slightly pinkish.
If you say 'to the right side of the screen' it sounds as if directfb
switches resolution at startup; you should run fbset -i in the same
terminal as your app, but that is quite impossible to do, so I would
advise to run dfbdump simultaneously instead, which also gives some data
on the currently selected format in the "layer" section. You need to
have configured with --enable-multi though, and a working fusion.ko.
dfbdump -dl can be interesting as well, this will dump the layer content
as DirectFB sees it, so you can load it gimp or so to check.
for the system-not-found issue, The DirectFB Makefile has a variable
called MODULEDIR; Your systems are then searched in
$(MODULEDIR)/systems. MODULEDIR can be overridden runtime by e.g.
--dfb:module-dir=<your location>.
hth
Niels
Pier Castonguay wrote:
Hello!
First sorry if this is a duplicate, seems like I had problem posting
the first time around.
I'm trying to port a xorg/gtk application to use directfb instead for
faster speed. I got DirectFB-1.3.1 from the git source (to fix the
armasm_memcpy error). I first tried to cross-compile and copy the libs
but when running an example application I had the "no system found"
error. So I compiled directly on the arm device. It took a few hours
but it finally worked and exemples (cross-compiled) now execute.
So I run df_matrix. Problem is, resolution and color depth it try to
use seems bad. Everything is gray/yellow and to the right side of the
screen.
fbset gives me this:
ts7000:~# fbset -i
mode "800x480-61"
# D: 31.500 MHz, H: 31.754 kHz, V: 61.066 Hz
geometry 800 480 800 480 16
timings 31746 128 24 28 9 40 3
rgba 5/11,5/5,5/0,0/0
endmode
Frame buffer device information:
Name : TS7370
Address : 0x60100000
Size : 768000
Type : PACKED PIXELS
Visual : MONO01
XPanStep : 0
YPanStep : 0
YWrapStep : 0
LineLength : 1600
MMIO Address: 0x600ff030
MMIO Size : 10
Accelerator : No
I then checked /etc/fb.modes but there was a list of un-related
resolution (imposible for this device). So I took the mode from fbset
and wrote it as the first one in this file. Unfortunately, no change
on df_matrix look. Startup messages looks a bit better (instead of
failing setting 2-3 modes, it say it accepted 800x480x16 directly, but
don't seems like it use it).
I also tried to run with arguments like –dfb :pixelformat=RGB16, but
no changes.
My framebuffer seems correct, because catting a fullscreen color
picture directly to /dev/fb0 works.
Also, if I start xorg, then open a console and start "df_matrix
--dfb:system=x11", it opens a new window and the colors are correct.
Still, the goal is to prevent the use of xorg.
Finally, when starting the application in the console (with bad
colors), and exiting with "esc", it completly freeze my display until
I either reboot, or connect to the device with telnet and execute
startx. This isn't normal isn't it?
Is there anything else I could check?
Thx
------------------------------------------------------------------------
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
