Re: 2.6.27-rc1: softcursor behaviour changed

[Stefano Stabellini <stefano.stabellini@eu.citrix.com>]

Pavel Machek wrote:

>> The problem is not a matter of taste but a matter of correctness: the
>> build_attr function in drivers/char/vt.c stores the blink attribute as
>> the forth bit of the background color.
>> Then in fbcon we are interpreting the same forth bit of the background
>> color as intensity bit.
> 
> ...which works pretty well. We can't reasonably blink in fbcon, so we
> highlight it with bright background, instead. Even old VGA had option
> to do that.
> 
>> My patch fixes that.
> 
> AFAICS high bit is now completely ignored now. That makes it
> useless...

- an application wants to do X
- I don't like X and X is not even implemented here
- let's do Y instead!

I think this is not the correct way of doing things, we could implement
blinking in fbcon instead.
In fact I posted another patch a while ago to implement blinking in
fbcon, but it wasn't accepted, not sure why yet :)
Maybe I'll try to talk with the fbcon devs to understand the problem
better, and reasonably soon you'll be able to see your blinking cursor
in fbcon.

> For example I can no longer see my cursor.
> 
> So, if 2.6.26 behaviour is "incorrect", can you show example where it
> matters, and how your patch "helps"?
> 


We have some ncurses applications that print a blinking white on blue
warning message.
Without the patch the message is static and with a pink background
(applications can change color settings, if they do that only for the
normal colors and not for the intensive colors because they think they
are not using them, this is what happens).