Index:
[thread]
[date]
[subject]
[author]
From: Andrew Apted <ajapted@netspace.net.au>
To : ggi-develop@eskimo.com
Date: Fri, 7 Aug 1998 12:52:05 +1000
Re: unresolve fb_display II
Jan writes:
> i don't know why but...
>
> i'm did it. the driver inserts fine now, con2fbmap fails with an oops.
>
> fbcon-kgi.c:980: Activating kgicon mode 640x400#640x0[8].
> fbcon-kgi.c:854: Activating success: 640x400#640x0 D1x1 [0x4]
> kgifb_init: xres 640 yres 400 bpp 8 vaddr 0xc387c000 paddr 0xe0000000 size 2097152
> fb1: KGI frame buffer device using 2048K of video memory
> fbcon-kgi.c:854: Activating success: 640x400#640x0 D1x1 [0x4]
> Unable to handle kernel paging request at virtual address c787c000
>
> why is (virt.y == 0) ??
That tells the KGI driver to maximum the virt.y value. It is mentioned
in the "display writer's guide", and it works here with my ET6000
driver, but I guess some drivers haven't implemented that feature ?
It definitely should not be 0 _after_ setting the mode (like it is
above), and I guess that confuses fbcon and causes the oops.
The reason we want the greatest virt.y is that it speeds up scrolling
greatly (by using YPAN mode).
Cheers,
_____________________________________________ ____
\ /
Andrew Apted <andrew@ggi-project.org> \/
Index:
[thread]
[date]
[subject]
[author]