Ok that's what I obtain in that examples:
df_dok:
df_dok.c <1156>:
(#) DirectFBError [dfb->CreateImageProvider( dfb,
DATADIR"/biglogo.png", &provider )]: File not found!
(!!!) *** WARNING [Application exited without deinitialization of DirectFB!]
*** [core.c:630 in dfb_core_deinit_check()]
df_andi:
df_andi.c <497>:
(#) DirectFBError [dfb->CreateFont( dfb, FONT, &desc, &font )]: File not
found!
(!!!) *** WARNING [Application exited without deinitialization of DirectFB!]
*** [core.c:630 in dfb_core_deinit_check()]
When I execute df_andi the screen goes black
If I execute df_cpuload I get a red square (not filled) on a pink screen. I
don't know if that is correct.
Thanks
El Sábado, 5 de Noviembre de 2005 09:12, Denis Oliver Kropp escribió:
> Quoting Iñaki de la Fuente:
> > I'm trying to compile and install directfb for an arm (mx21 machine).
> > I've crosscompiled it with:
> >
> > ./configure --prefix=/home/inaki/fb_build/ --disable-x11 --enable-fbdev
> > --disable-video4linux
> > make
> > make install
> >
> > The problem is when I execute any dfb binary (for instance dfbinfo), I
> > get the following message:
> >
> > # dfbinfo
> >
> > ---------------------- DirectFB v0.9.24 ---------------------
> > (c) 2000-2002 convergence integrated media GmbH
> > (c) 2002-2004 convergence GmbH
> > -----------------------------------------------------------
> >
> > (*) DirectFB/Core: Single Application Core. (2005-11-04 11:21)
> > fbcon_setup: No support for fontwidth 8
> > fbcon_setup: type 0 (aux 0, depth 16) not supported
>
> That's from the kernel.
>
> > (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 117)...
> > (!) DirectFB/FBDev: couldn't access /proc/bus/pci/devices!
> > --> No such file or directory
>
> This can be ignored.
>
> > (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 118)...
> > (!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:797]
>
> This one, too.
>
> > (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
> > (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 119)...
> > (*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH)
> > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (convergence
> > integrated media GmbH)
> > (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
> >
> >
> > Screen (00) FBDev Primary Screen (primary screen)
> > Caps: VSYNC POWER_MANAGEMENT
> >
> > Layer (00) FBDev Primary Layer (primary layer)
> > Type: GRAPHICS
> > Caps: SURFACE BRIGHTNESS CONTRAST SATURATION
> >
> >
> > Input (00) Keyboard (primary keyboard)
> > Type: KEYBOARD
> > Caps: KEYS
> >
> > Input (01) IMPS/2 Mouse (primary mouse)
> > Type: MOUSE
> > Caps: AXES BUTTONS
> > Max. Axis: 2
> > Max. Button: 2
> >
> >
> > Can you help me?
>
> Your dfbinfo ran fine.
> Did you try some of the DirectFB-examples, like df_dok or df_andi?
>
> > My framebuffer seems to work correctly, here you can see fbset -i
> > # fbset -i
> >
> > mode "240x320-76"
> > # D: 5.830 MHz, H: 24.292 kHz, V: 75.914 Hz
> > geometry 240 320 240 320 16
> > timings 171521 0 0 0 0 0 0
> > rgba 4/8,4/4,4/0,0/0
> > endmode
>
> Interesting, RGB444 (supported via ARGB4444).
>
> > Frame buffer device information:
> > Name : dbmx21
> > Address : 0xc2f99000
> > Size : 153600
> > Type : PACKED PIXELS
> > Visual : TRUECOLOR
> > XPanStep : 0
> > YPanStep : 0
> > YWrapStep : 0
> > LineLength : 480
> > Accelerator : No
>
> Hmm, just enough memory for the front buffer.
> The example program df_andi should use a back buffer
> in system memory as a fallback. If it doesn't work,
> please let me know.
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
