On Sat, 19 Nov 2005 11:30:07 +0200, "Ville Syrjälä" <[EMAIL PROTECTED]>
said:
> 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/FBDev: No supported modes found in /etc/fb.modes and
> > current mode not supported!
> 
> The driver didn't accept your /etc/fb.modes.

/etc/fb.modes contains the output from fbset...
 
> > (!) 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

It seems to be the same driver.  I've applied some patches for CSTN
16/8-bit...  I think I accidentally sent the output to the list from
when I using 16-bit.  Anyhow, the same error occurs for 8 or 16-bit.

> 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.

The system is based upon busybox, so I think the output from fbset may
be slightly different.  Is there anyway to enable more debugging prints,
function calls etc or do I have to manually add printfs to DirectFB to
determine the cause of the problem?

NB, the bpp of the driver comes from the lcd-panel.h definitions...

Also, does DirectFB use another section of memory for a shadow
framebuffer or does it just deal directly with the framebuffer?

I've re-run this again, with the 8-bpp kernel driver:

/ # fbset

mode "320x240-1"
        # D: 0.050 MHz, H: 0.155 kHz, V: 0.642 Hz
        geometry 320 240 320 240 8
        timings 20000000 1 1 0 0 1 1
        accel false
        rgba 8/0,8/0,8/0,0/0
endmode

/ # dfbinfo

       ---------------------- 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, 786)...
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 787)...
 (!!!)  *** 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 m
edia GmbH)
(!) DirectFB/FBDev: No supported modes found in /etc/fb.modes and
current mode n
ot supported!
(!) DirectFB/FBDev: Current mode's pixelformat: rgba 8/0, 8/0, 8/0, 0/0
(8bit)
(!) DirectFB/Core/layers: Failed to initialize layer 0!
    --> Initialization error!
(!) DirectFB/Core: Could not initialize 'layers' core!
    --> Initialization error!
(#) DirectFBError [DirectFBCreate() failed]: Initialization error!

/ # cat /etc/fb.modes

mode "320x240-1"
        # D: 0.050 MHz, H: 0.155 kHz, V: 0.642 Hz
        geometry 320 240 320 240 8
        timings 20000000 1 1 0 0 1 1
        accel false
        rgba 8/0,8/0,8/0,0/0
endmode

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to