[vdr] Re: VGA output, what is the best solution?

[Nicolas Huillard <nhuillard@ghs.fr>]

Mattias Viberg a écrit :
...
> (*) DirectFB/Core: Single Application Core. (with MMX support)
> (2004-10-22 00:35)
> (*) Direct/Memcpy: Using MMXEXT optimized memcpy()
> (*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 21138)...
> (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 21140)...
> (*) DirectFB/Input: IMPS/2 Mouse (1) 0.9 (convergence integrated media
> GmbH)
> (*) Direct/Thread: Running 'PS/2 Input' (INPUT, 21141)...
> (*) DirectFB/Input: IMPS/2 Mouse (2) 0.9 (convergence integrated media
> GmbH)
> (*) Direct/Thread: Running 'Keyboard Input' (INPUT, 21142)...
> (*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
> (*) DirectFB/Genefx: MMX detected and enabled
> (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence
> integrated media GmbH)
> (*) DirectFB/WM: Default 0.1 (Convergence GmbH)
I don't see the name of the graphics driver used : check what options 
you could put inside /etc/directfbrc to use you video card. This driver 
is a DirectFB driver that is meant to used accelerated functions 
implemented by the kernel frame-buffer module (which must be loaded 
first, of course).

> [dfb] RAM: 33554432 bytes
> [dfb] Accellerated Functions:
> [dfb] Drawing Flags: none
> [dfb] Surface Blitting Flags: none
> [dfb] Supported video Modes are: 1024x768@16
Supported video modes are only 32 bits for softdevice : check 
/etc/fb.modes, the fbset command (fbset -i, fbset --depth 32, etc.) and 
/etc/directfbrc.
My conf is in previous mails either on the ML, or on the directfb-users ML.

> [dfb] Enumeratig display Layers
> Layer 0 FBDev Primary Layer  Type: graphics
>   Caps: brightness contrast saturation surface
> (!) [21135:    0.000] --> Caught signal 11 (at 0x4, invalid address) <--
Might be caused by the 16bpp.

--
NH