Thread (5 messages) 5 messages, 3 authors, 2005-11-15

Re: fbcon bug?

From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: 2005-11-14 20:11:01

Ville Syrjälä wrote:
On Sun, Nov 13, 2005 at 09:24:36PM -0500, Zack Smith wrote:
quoted
Hi all,

I've noticed that 2.6.14, when a console switch occurs going
from a console that is KD_TEXT to one that is KD_GRAPHICS,
fbcon doesn't seem to immediately shut down the cursor. It appears
to draw or undraw the cursor at least once before it disables
cursor activity due to graphics mode.

Does anybody know if this bug has been corrected in 14.1 or .2,
or if anyone would mind if I go in and fix it?
I'm not sure if it's related but there is a cursor problem with atyfb. 
When doing ioctl(... KD_GRAPHICS) the cursor remains visible in most 
cases. Sometimes it does disappear properly but that is quite rare. 
However doing a vt switch to another vt and back again seems to fix it 
every time so I'm not sure it's the same problem you're seeing. None of 
the other fb drivers I use implement a hardware cursor which is probably 
the reason I'm only seeing it on atyfb.
Once the console is in KD_GRPHICS mode, all access the to the framebuffer
are essentially stopped.  So depending on the state of the cursor (visible
or not), it will stay that way even if a command to erase or draw the
cursor is given.

You may tell the console to erase the cursor before going to KD_GRAPHICS
mode as a workaround.

Tony



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help