Hi,
today I tried the DirectFBGL module. I grabbed the cvs source aswell as the
Mesa source from http://www.sci.fi/~syrjala/gl/ (since I run 2.6.6 on that
machine).
Everything compiled ok afaik and installation was exactly as described in
the readme. Then I tried running df_gears. The screen went completely white
and on the most top row I saw some pixels moving (red pixels). I checked
video modes and everything and it was ok (DFBTerm runs fine for example and
so does DFBSee).
I have DirectFB-0.9.21 from CVS with multi-app core and a Matrox G200. I
remember running DirectFBGL-0.9.12 in the past just fine, so either I broke
something or somethings wrong ;)
Anyway, here's my console log:
(*) DirectFB/Config: Parsing config file '/root/.directfbrc'.
---------------------- DirectFB v0.9.21 ---------------------
(c) 2000-2002 convergence integrated media GmbH
(c) 2002-2004 convergence GmbH
-----------------------------------------------------------
(*) DirectFB/Core: Multi Application Core. (with MMX support) (2004-05-21
22:15)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'Fusion Dispatch' (MESSAGING, 6093)...
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 6096)...
(*) DirectFB/Input: IMPS/2 Mouse (1) 0.9 (convergence integrated media GmbH)
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 6097)...
(*) DirectFB/Input: IMPS/2 Mouse (2) 0.9 (convergence integrated media GmbH)
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 6098)...
(*) DirectFB/Input: IMPS/2 Mouse (3) 0.9 (convergence integrated media GmbH)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 6099)...
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: Matrox G200 0.7 (convergence integrated media GmbH)
(!!!) *** WARNING [no video mode set yet] *** [layers.c:536 in
dfb_screen_rect
angle()]
(!!!) *** WARNING [no video mode set yet] *** [layers.c:536 in
dfb_screen_rect
angle()]
(*) Direct/Interface: Loaded 'Default' implementation of 'IDirectFBFont'.
(*) Direct/Interface: Loaded 'DRI' implementation of 'IDirectFBGL'.
(*) DirectFB/DRI: probed chipset 0x521
[drm] added 8192 byte SAREA at 0xf1b81000
[drm] mapped SAREA 0xf1b81000 to 0x43752000, size 8192
[drm] framebuffer handle = 0xe3000000
[agp] Mode 0x1f000207 [AGP 0x8086/0x7190]
[agp] Mode 0x1f000203 [AGP 0x8086/0x7190]
[drm] Enabling AGP 2x PLL encoding
[agp] 65536 kB allocated with handle 0x00000001
[agp] WARP microcode handle = 0xe4000000
[agp] WARP microcode mapped at 0x43754000
[agp] Primary DMA handle = 0xe4008000
[agp] Primary DMA mapped at 0x4375c000
[agp] DMA buffers handle = 0xe4108000
[agp] DMA buffers mapped at 0x4385c000
[drm] Added 128 65536 byte DMA buffers
[agp] agpTexture handle = 0xe4908000
[agp] agpTexture size: 53248 kb
[drm] Registers handle = 0xe2000000
[drm] Status handle = 0xf1ba5000
[agp] Status page mapped at 0x4405c000
Using 64 MB AGP aperture
Using 8 MB for vertex/indirect buffers
Using 52 MB for AGP textures
Will use 0 kb for textures at offset 8.0 MB
[drm] Mapped 128 DMA buffers
[drm] got IRQ 16
[drm] dma control initialized, using IRQ 16
chipset: 1
mem: 0
agpMode: 2
textureOffset: 8388608
textureSize: 0
logTextureGranularity: 16
logAgpTextureGranularity: 22
agpTextureHandle: 3834675200
agpTextureSize: 54525952
mgaEngineRestore() is not yet implemented!
I noticed the warnings about the video modes, but as I wrote, all other DFB
apps run just fine. Am I missing something or is something broken?
cheers,
Roel Baardman
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-dev" as subject.
