From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Gerd Knorr <kraxel@bytesex.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-fbdev-devel] cursor bug
Date: Tue, 9 Nov 2004 10:37:50 +0800 [thread overview]
Message-ID: <200411091037.52418.adaplas@hotpop.com> (raw)
In-Reply-To: <20041108161113.GA23504@bytesex>
On Tuesday 09 November 2004 00:11, Gerd Knorr wrote:
> Hi,
>
> There is annonying cursor bug in recent kernels (started in 2.6.10-rc1
> IIRC). There kernel seems not to keep track of the cursor state
> correctly when switching virtual terminals. Here is how to reproduce
> it:
>
> (1) boot with vesafb (thats what I'm using, maybe it shows on other
> framebuffers and/or vgacon as well).
> (2) login into one terminal, then type "echo -ne '\033[?17;15;239c'".
> You should have a nice, yellow and *not* blinking cursor block.
> That is what I have in my .profile because I can't stand the
> blinking cursors.
> (3) Switch to another terminal. The cursor goes into blinking
> underscore mode now (i.e. the default cursor).
> (4) Switch back to the first terminal. Now you have a yellow block
> with the last two pixel lines (i.e. the underscore) blinking.
>
> Oh no. Please fix that. Thank you.
Hmn, this bug has been present since the beginning of 2.6, probably even
2.5, hidden, but got exposed during the cursor cleanup. The main problem is
that fbcon is not checking if the vt is using its own softcursor, and this
has been the case since the fb architecture was rewritten.
We fix this by checking if vt.c is using its softcursor
(vc->vc_cursor_type & 0x10), and if true, disable fbcon cursor.
I'll submit a patch to Andrew.
Tony
prev parent reply other threads:[~2004-11-09 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 16:11 cursor bug Gerd Knorr
2004-11-09 2:37 ` Antonino A. Daplas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411091037.52418.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=adaplas@pol.net \
--cc=kraxel@bytesex.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).