Xfree86-4.0.1, Lombard, Mach64 driver, X-server Crash

[Takashi Oe]

On Thu, 28 Sep 2000, Geert Uytterhoeven wrote:

> > My understanding is this:
> > Video console uses 16 colors, and it only initializes the cmap
> > corresponding to those 16 colors.  The other entries in cmap are up to
> > each individual fb driver or undefined as far as console is concerned.
> > For software cursor, driver specific (struct display_switch *)ops->revc()
> > is used to make the cursor blink.  For the generic fbcon_cfb{16,32}_revc,
> > it xors each pixel with masks 0xffff (depth 16) or 0xffffffff (depth 32).
> > For controlfb which I am very familiar with, the "correct" masks are
> > 0x3def for 555 and 0x0f0f0f0f for 8888.  That is, only 4 LSBs or low 16
> > for each red, green, and blue are xor'ed since cmap entries corresponding
> > to higher bits are undefined as far as fbcon support is concerned.
>
> In 2.5.x, we'll have a user-defined xor mask for the cursor as the 17th entry
> in the dispsw_data array.

Can we put it for 2.4?  As far as I can see, the actual size of
dispsw_data matters only between fb driver and fbcon-cfbxx.c, and the
changes required for each driver seem to be rather small.  Besides,
controlfb is not the only one which will benefit from this change.


Takashi Oe


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/