linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK FBDEV] A few more updates.
Date: 26 Mar 2003 18:20:19 +0800	[thread overview]
Message-ID: <1048673964.1025.37.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0303260519380.12718-100000@phoenix.infradead.org>

On Wed, 2003-03-26 at 13:34, James Simmons wrote:
> 
> > 3.  BTW, there are too many kmalloc's/kfree's in accel_cursor() and
> > softcursor().  Personally, I would rather have 2 64-byte buffers for the
> > mask and the data in the info->cursor structure than allocating/freeing
> > memory each time the cursor flashes.  However, if you prefer doing it
> > this way, the patch also includes changes so kmallocs are only done when
> > necessary.  Still, accel_cursor() has unnecessary work being done, such
> > as always creating the mask bitmap, when a simple flag to monitor cursor
> > shape changes could prevent all this.
> 
> I agree. The problem is the upper layer of the console system is to brain 
> dead. Its either erase the cursor or redraw it again. There is no way to 
> just say cursor just moved. There is a CM_MOVE but the upper layer doesn't 
> even use it :-( If you look at vgacon and friends you will see they 
> recreate the cursor every time the cursor blinks. Yes even vgacon.c does 
> this. It is stupid and brain dead but that is the way the upper layers of 
> the console work. The correct solution would be to use actually use 
> CM_MOVE in the upper layers.

Even so, (and I don't really fault the console cursor as it only needs
to show, hide and move the cursor), accel_cursor() can easily monitor
shape changes.  We can use a bitfield somewhere in fb_cursor(perhaps the
high 8 bits of info->fb_cursor.set?) to "remember" the current cursor
shape.

Tony




-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

  parent reply	other threads:[~2003-03-26 10:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 18:32 [BK FBDEV] A few more updates James Simmons
2003-03-25 18:01 ` Russell King
2003-03-25 18:04   ` James Simmons
2003-03-25 18:28 ` Benjamin Herrenschmidt
2003-03-25 18:35   ` Benjamin Herrenschmidt
2003-03-25 19:48     ` James Simmons
2003-03-25 20:10       ` Benjamin Herrenschmidt
2003-03-25 20:14         ` James Simmons
2003-03-25 18:44   ` James Simmons
2003-03-26  3:37 ` Antonino Daplas
2003-03-26  5:34   ` James Simmons
2003-03-26  9:53     ` Antonino Daplas
2003-03-26 10:20     ` Antonino Daplas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-26 10:42 Petr Vandrovec
2003-03-26 11:20 ` Antonino Daplas
2003-03-26 10:53 Petr Vandrovec

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=1048673964.1025.37.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=jsimmons@infradead.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).