Thread (12 messages) 12 messages, 3 authors, 2005-11-22

Re: 2 more fbcon rotation bugs

From: Knut Petersen <hidden>
Date: 2005-11-19 10:12:47

Antonino A. Daplas schrieb:
quoted
For rotation values of 1 and 3 in combination with unusual font heights
there are
serious cursor problems:
   
This one I cannot reproduce. Have you tried reproducing it with vesafb?
Any message in the log, such as a kernel oops?  Your description sounds
like a corruption of cursor->mask and cursor->image.data.
 
I tried to reproduce it with vesafb ... vesafb does not show this bug. 
Reproducability with cyblafb
is 100%. But cyblafb does not provide cursor functions, so both really 
should show the same
behaviour, shouldn´t they? No messages in the log, no oops, no side 
effects. Screen is restored
to the correct display if the gpm mouse cursor or the normal cursor is 
moved to the wrong character
cell.

New bug: Vesafb & rotation does show a bug that is not present using 
cyblafb & rotation and the 16x30
bitstream font: When I start my favourite text editor sedt, the top row 
is coloured and contains some
status information. Line two is in a different colour. Those areas of 
line 1 drawn with the bitblit
functions are ok, but those areas drawn with the fillrect function are 
not completely coloured, the last
(maybe the 2 last, don´t know) pixel rows of the area that should be 
coloured are still black.

Additional bug: I am used to compile vesafb into the kernel and to load 
and remove the cyblafb
module during the developement process, switching to and from vesafb 
using con2fb. That´s still
possible with rotation == 0, but it locks the computer if at least one 
framebuffer is set to rotation 1.
I have not tested that for rotation == 2 or 3.
You can also try enabling a non-blinking block cursor
(Documentation/VGA-softcursor.txt) to isolate the problem. With a
non-blinking block cursor, fbcon's cursor is disabled and vt.c's softcursor
takes over.  

You also said that the cursor becomes fixed.  You can comment out the call
to ops->cursor in fb_flashcursor in fbcon.c so you get a fixed cursor and
eliminate the cursor blink pathway from the debugging.

Tony

 
As you cannot reproduce the cursor/delete bug, I´ll try to find the 
cause and to fix it then. Please
have a look at the other bugs.

cu,
 Knut





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help