[Linux-fbdev-users] Re: [directfb-users] Re: 1400x1050 not possible with ATI M9?

[Torgeir V. <to...@po...>]

On Sat, 2005-01-22 at 19:26 -0500, Taoufik Zammou wrote:
> On Fri, 21 Jan 2005 15:32:44 +0000, Torgeir Veimo <to...@po...> wrote:
> > 
> > What does fbset -i tell you?
> > 

> - When recompiling DirectFB without multi-app support (fusion),
> DirectFB works in 1400x1050.
> - When compiled with multi-app, DirectFB crashes on 1400x1050...
> whatever the refreshrate is. I've tried 1400x1050@62 and 1400x1050@75.
> Both worked good with fbset (console). Running DirectFB with the last
> one gave screen for a half a second, there after i get the "Caught
> signal 7" error. Running DirectFB with the fist one, DirectFB exists
> immediatly with the "Caught signal 7" error.
> 
> So it seems it has something to do with the fusion kernel module.
> 
> fbset -i tells this:
> 
> mode "1400x1050-62"
>     # D: 108.003 MHz, H: 65.856 kHz, V: 61.778 Hz
>     geometry 1400 1050 1400 1050 8
>     timings 9259 88 40 13 0 112 3
>     hsync high
>     vsync high
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> Frame buffer device information:
>     Name        : ATI Radeon Lf
>     Address     : 0xe8000000
>     Size        : 33554432
>     Type        : PACKED PIXELS
>     Visual      : PSEUDOCOLOR
>     XPanStep    : 8
>     YPanStep    : 1
>     YWrapStep   : 0
>     LineLength  : 1408
>     MMIO Address: 0xfcff0000
>     MMIO Size   : 16384
>     Accelerator : No

You probably need to patch the radeon fb driver to explicitly set an
accelerator id to get directfb working properly. What is the output of
running dfbinfo?

[root@vigor10 aty]# diff radeon_base.c radeon_base.c-orig
1783,1784d1782
<       else
<               info->fix.accel = FB_ACCEL_ATI_RADEON;

-- 
Torgeir Veimo <to...@po...>