On Mon, Apr 03, 2000 at 10:06:58PM +0200, Eddie C. Dost wrote:
> > 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.
Well, I've never experienced this before. One thing I did change was that
X has always been running at 76Mhz, and fb was at 85Mhz. I changed the
modeline for X to the one I got from fbset -X, that way they would be no
flicker when swapping from X to console.
Not sure if this helps, but who knows...
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
