Re: [directfb-users] viafb SLOW, not working accellerated

vdrgeorge Mon, 05 Dec 2005 07:11:19 -0800

I also experience identical results as Dave with my KM400 chipset motherboard with integrated unichrome video. My log files are similar to what Dave posted.

I am using Gentoo 2005.1-r1 with:

kernel = 2.6.14-gentoo-r4

gcc = 3.3.5-20050130

DirectFB's linux-viafb driver CVS - 12/03/05

DirectFB CVS - 12/03/05

DFB++ CVS - 12/03/05

softdevice CVS - 12/03/05

In fact, the moment that I load the viafb driver, my terminal window becomes corrupt and unusable. However if I connect via SSH, I can start vdr with softdevice via DFB and the OSD displays normaly, however the same thin band of video corruption in the upper 1/4 screen is encountered as Dave discribed.

------

dmesg output when viafb module is loaded:

viafb: VIA UNICHROME framebuffer 1.0 initializing
viafb: viafb : DEA00000
viafb: framebuffer size = 32 Mb
viafb: Found Device Rev:0
mtrr: MTRR 4 not used
mtrr: base(0xe0000000) is not aligned on a size(0x2080000) boundary
viafb: X:800 Y:600
viafb: mode=800 bpp=32 refresh=255 TVon=0 TVtype=2
viafb: VQ start:2040000 end:207FFFF size:40000
viafb: Cursor start:203F000 end:203FFFF size:1000
viafb: mode=800 bpp=32 refresh=255 TVon=0 TVtype=2
viafb: irq handler installed, IRQ(0x200) = 80080402
fb0: UNICHROME frame buffer device
------

dfbinfo output (I currently have an empty /etc/directfbrc):

       ---------------------- DirectFB v0.9.25 ---------------------
             (c) 2000-2002 convergence integrated media GmbH
             (c) 2002-2004 convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2005-12-03 19:44)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
(*) Direct/Thread: Running 'VT Switcher' (CRITICAL, 9141)...
(*) Direct/Thread: Running 'LiRC Input' (INPUT, 9145)...
(!!!) *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:837]
(*) DirectFB/Input: LIRC Device 0.2 (convergence integrated media GmbH)
(*) Direct/Thread: Running 'PS/2 Input' (INPUT, 9156)...
(*) DirectFB/Input: IMPS/2 Mouse 1.0 (Convergence GmbH)
(*) Direct/Thread: Running 'Keyboard Input' (INPUT, 9157)...
(*) DirectFB/Input: Keyboard 0.9 (convergence integrated media GmbH)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: VIA/S3G KM400/UniChrome 0.4 (-)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)

Screen (00) FBDev Primary Screen (primary screen)
Caps: VSYNC POWER_MANAGEMENT

     Layer (00) VIA CLE266 Graphics             (primary layer)
        Type:    GRAPHICS
        Caps:    SURFACE OPACITY ALPHACHANNEL SRC_COLORKEY BRIGHTNESS CONTRAST SATURATION

     Layer (01) VIA Unichrome Video
        Type:    GRAPHICS VIDEO STILL_PICTURE
        Caps:    SURFACE OPACITY SCREEN_LOCATION DEINTERLACING DST_COLORKEY LEVELS FIELD_PARITY SCREEN_POSITION SCREEN_SIZE

     Layer (02) VIA Unichrome DVD Subpicture
        Type:    GRAPHICS VIDEO STILL_PICTURE
        Caps:    SURFACE OPACITY
----

regards,

george

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

Re: [directfb-users] viafb SLOW, not working accellerated

Reply via email to