On Thu, Nov 17, 2005 at 03:55:40PM +1000, Hasjim Williams wrote: > Hi everyone, > > I'm having troubles getting DirectFB to run on the LH7A400. It uses a > ARM PL110 LCD controller. However, I can't seem to get it to run. I > compiled this using OpenEmbedded... Does colour depth / resolution need > to be settable through DirectFB? This is running on an 8-bit 320x240 > display... I did originally have some problems with Keith's kdrive X > server, and needed to apply the same patches that are used on Poodle: > > - k = ioctl (priv->fd, FBIOPUT_VSCREENINFO, &var); > + /* k = ioctl (priv->fd, FBIOPUT_VSCREENINFO, &var); */ > > (org.openembedded.dev/packages/xserver/xserver-kdrive/xserver-kdrive-poodle.patch). > > I've also set /etc/fb.modes to contain the same output as "fbset". > > Also has anyone written any other Drivers for other embedded video > controllers, eg http://tree.celinuxforum.org/CelfPubWiki/PortDirectFB > ??? > > Thanks for any help that anyone can offer... > > ---------------------- DirectFB v0.9.22 --------------------- > (c) 2000-2002 convergence integrated media GmbH > (c) 2002-2004 convergence GmbH > ----------------------------------------------------------- > > (*) DirectFB/Core: Single Application Core. (2005-11-17 05:02) > (*) Direct/Threadlh7a40x_clcd_mmap > : Running 'VT Switcher' (CRITICAL, 855)... > (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 856)... > (!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802] > (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH) > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (convergence > integrated media GmbH) > (!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and > current mode not supported!
The driver didn't accept your /etc/fb.modes. > (!) DirectFB/FBDev: Current mode's pixelformat: rgba 5/0, 6/5, 5/11, 0/0 This tells us you're running in 16bit mode. What does fbset print? Is this is the driver you're using? http://www.home.arm.linux.org.uk/developer/patches/viewpatch.php?id=2015/1&LoginID=cf40a012069831f0cd39970ff34481c1 AFAICS that driver accepts all offered modes which means that it can't be the FBIOPUT_VSCREENINFO ioctl() that fails. The only reason for the failure that I can think of is that you have forced the pl110fb driver to 8bpp with the depth option but now were offering it a 16bpp mode but there isn't enough video memory available for that mode since the driver allocates video memory based on the initial depth option. That means there is a bug in the pl110fb driver. It should not accept a 16bpp mode if it doesn't have enough memory for it. It also means that something very strange is going one because somehow the driver is running in 8bpp mode but it tells us that it's running in 16bpp. -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
