Srinivas Rao M Hamse wrote: > Hi Shrikanth, > > Thanks for the reply, After giving dfbinfo with the said arguments i am > getting the following output with no change on screen. > > > # ./dfbinfo --dfb:system=devmem --dfb:video-phys=0x83000000 > --dfb:video-length=691200 > > =======================| DirectFB 1.1.1 |======================= > (c) 2001-2007 The DirectFB Organization (directfb.org) > (c) 2000-2004 Convergence (integrated media) GmbH > ------------------------------------------------------------ > > (*) DirectFB/Core: Single Application Core. (2007-12-28 13:56) [ DEBUG ] > (!) Davinci/Driver: FBIO_GET_TIMING failed! > --> Invalid argument
The proprietary davincifb ioctl FBIO_GET_TIMING is used to probe for the driver, because there's no accelerator id. If that ioctl fails the DirectFB driver will not be used. I had that effect after removing the sizeof() from the ioctl definitions so I've put them back. If you put your original ioctl definitions from your running kernel from linux-kernel/include/linux/davincifb.h into DirectFB/gfxdrivers/davinci/davincifb.h it should work. You can also try the complete file, but I wonder what could be that different on your system. Don't you use the 2.6.10 Montavista Kernel? > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org) > (*) DirectFB/Core/WM: Default 0.3 (directfb.org) > (!) IDirectFB_Construct: No layers available! Missing driver? The devmem system module does not provide any layer implementation as opposed to the fbdev system module. If there's no driver, there's no layer and DirectFB is not functional. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
