There are some patches to intelfb drivers in the latest kernel.
I downloaded and compiled kernel version 2.6.22.5 and it kind of works.
fbset -i now show me these:
mode "1024x768-76"
# D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
geometry 1024 768 1024 768 32
timings 12714 128 32 16 4 128 4
rgba 8/16,8/8,8/0,8/24
endmode
Frame buffer device information:
Name : VESA VGA
Address : 0x98000000
Size : 6291456
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 0
YPanStep : 0
YWrapStep : 0
LineLength : 4096
Accelerator : No
dfbinfo shows me some information which I cannot really understand or bother
with for now.
It at least runs without complaining anymore.
Next, I needed a demo program to show the "power" - speed of DirectFB.
I downloaded gtktetris from http://www.gnomefiles.org/app.php/gtktetris and
compiled it without problem.
When I run it, I noticed that the blocks are not refreshing correctly.
Switching between console will cause it to update the block new location.
The console shows the following error messages, running dfblayer shows
similiar messages too.
# gtktetris-0.6.2/gtktetris
=======================| DirectFB 1.0.0 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2007-08-29 00:53)
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 3427)...
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 3428)...
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 3429)...
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 3430)...
(*) DirectFB/Input: SynPS/2 Synaptics TouchPad (1) 0.1 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 3431)...
(*) DirectFB/Input: AT Translated Set 2 keyboard (2) 0.1 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 3432)...
(*) DirectFB/Input: Power Button (FF) (3) 0.1 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 3433)...
(*) DirectFB/Input: Sleep Button (CM) (4) 0.1 (directfb.org)
(*) Direct/Thread: Running 'Linux Input' (INPUT, 3434)...
(*) DirectFB/Input: Lid Switch (5) 0.1 (directfb.org)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(!) DirectFB/FBDev: Panning display failed!
--> Invalid argument
Output of dmesg shows a disturbing "Cannot reserve FB region" error message.
Are these 2 errors related?
# dmesg |grep intelfb
intelfb: intelfb_init
intelfb: Framebuffer driver for Intel(R)
830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
intelfb: Version 0.9.4
intelfb: intelfb_pci_register
intelfb: fb aperture: 0x98000000/0x8000000, MMIO region: 0x90400000/0x80000
intelfb: Cannot reserve FB region.
intelfb: cleanup
Do I need to specially tweak GtkTetris or any other Gtk+ application to get
it to work correct on DirectFB?
Seems like all the games (running on X/GNOME) that came pre-installed with
CentOS does not get drawn properly too.
Raymond Pau
----- Original Message -----
From: "Ville Syrjälä" <[EMAIL PROTECTED]>
To: "Raymond Pau" <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Tuesday, August 28, 2007 3:10 PM
Subject: Re: [directfb-dev] Need help setting up DirectFB
On Tue, Aug 28, 2007 at 11:05:01AM +0800, Raymond Pau wrote:
> I got these messages in /var/log/messages.
>
> # dmesg |grep intelfb
> Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
> video=intelfb:mode=1024x768-32,accel=0 vga=0x318
> intelfb: Framebuffer driver for Intel(R)
> 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
> intelfb: Version 0.9.4
> intelfb: 00:02.0: Intel(R) 855GM, aperture size 128MB, stolen memory
> 8060kB
> intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode
> switching.
> intelfb: Initial video mode is [EMAIL PROTECTED]
> intelfb: Changing the video mode is not supported.
> intelfb: Changing the video mode is not supported.
>
> Seems like intelfb driver doesn't like mode switching; anyway to tell
> directfb not to change mode?
In this case it doesn't switch the mode. It just tries to clear the
accel flag of the current mode. A quick glance at intelfb source suggests
that it should work. AFAICS that error message may come from two different
places in the driver and it may be perfectly normal w/ LVDS.
> Both accel=0 and noaccel does not seems to have any effect.
Does fbset still show 'accel = true'? If it's still true try to disable
it with fbset prior to running your DirectFB application. That should in
theory make the old and new modes identical. If that doesn't work I
guess we'll need to add some debug prints to dump the modes at some
critical points in the code.
--
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
