> Date: Mon, 3 Apr 2000 10:26:10 +0200 (MET DST)
> From: Geert Uytterhoeven <[EMAIL PROTECTED]>
>
> That's also my suggestion. BTW, how come no one ever found out
> before on SPARC64?
>
> Almost certainly because I tend to use a Creator3D framebuffer on all
> of my 2.3.x test systems here :-)
No, aty mach64 does not use fbcon_cfbX_bmove() and fbcon_cfbX_clear(), it
uses it's own routines. Something must have installed the fbcon_cfbX_*()
routines when he left X. Usually atyfb never calls fb_mem*() functions.
Anyway, I put a sample implementation using fb_readX/writeX in cvs.
During testing I saw some oddity with atyfb:
Doing a 'cat <largefile>' takes about say 30 seconds. Doing a scroll-up and
scroll-down using <SHIFT>-<PGUP>, <SHIFT>-<PGDN> before the 'cat <largefile>'
speeds it up to about 3 seconds. Something not initialized properly???
Eddie C. Dost
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
