On Wed, 8 Nov 2000, Michael Schmitz wrote:
> > > Happens sometime, for reasons yet unknown. What seems to happen is
> > > that the cursor changes color to black. Feel free to look up where
> > > the cursor color gets set, and pepper the fbcon code with printk to find
> > > where it goes wrong.
> >
> > However, the reason is known: the fbcon-* code draws the cursor by xor'ing
> > the
> > pixel values with a mask consisting of all 1's. This is not correct for
> > directcolor modes (e.g. 16, 24 and 32 bpp on ATI Mach64), where the color of
> > the cursor depends on what leftovers are present in the palette registers.
>
> Must be yet another reason for the invisible cursor: atyfb uses
> the hardware cursor :-) Any idea why setting the cursor color sometimes
> won't work? The cursor color gets set pretty early, maybe the chip needs
> some more init, or it isn't idle at that stage?
You're right. This is valid only for software cursors.
Note that even when using a hardware cursor, inverting characters (by e.g.
selection or gpm) is still influenced by the bug.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
