linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: adaplas@pol.net,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: PATCH: move soft_cursor into fbconsole
Date: Fri, 24 Jun 2005 08:26:14 -0400	[thread overview]
Message-ID: <9e473391050624052640aa5279@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0506240015300.24330@pentafluge.infradead.org>

On 6/23/05, James Simmons <jsimmons@www.infradead.org> wrote:
>         Now I was thinking instead of a massive move of the the software
> cursor we add a flag FBINFO_HWACCEL_CURSOR to tell us if we are using a
> hardware cursor. This way for the sysfs interface you can test to see if
> it is a hardware cursor and only allow userland to access a hardware
> cursor. Here is a patch for that. People please try it out.

Your code will work, but it is conceptually what we want to do?
Software cursors are application specific. The soft cursor implemented
in fbdev really belongs to fbconsole.  If we get another in-kernel
user with a different update pattern (maybe they use the GPU) they
will want a different soft cursor. Shouldn't we just move the current
soft cursor into fbconsole? Given that software cursors are
application specific fbdev should not contain one.

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click

  reply	other threads:[~2005-06-24 12:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-11  4:57 PATCH: move soft_cursor into fbconsole Jon Smirl
2005-06-11  6:15 ` James Simmons
2005-06-11 13:10   ` Jon Smirl
2005-06-11 13:23   ` Jon Smirl
2005-06-11 20:35 ` Geert Uytterhoeven
2005-06-11 22:01   ` Jon Smirl
2005-06-12  7:43     ` Geert Uytterhoeven
2005-06-16  1:34       ` Jon Smirl
2005-06-16  3:11         ` Antonino A. Daplas
2005-06-16  3:37           ` Jon Smirl
2005-06-21  0:07             ` James Simmons
2005-06-21  0:31               ` Jon Smirl
2005-06-24  0:09                 ` James Simmons
2005-06-24 12:26                   ` Jon Smirl [this message]
2005-06-24 16:17                     ` James Simmons
2005-06-24 16:27                       ` Jon Smirl
2005-06-24 17:13                         ` James Simmons
2005-06-24 17:25                           ` Jon Smirl
2005-07-01 23:32                             ` James Simmons
2005-07-01 23:52                               ` Sylvain Meyer
2005-07-06 23:28                                 ` James Simmons
2005-07-02  0:28                               ` Jon Smirl
2005-07-02  0:56                               ` Jon Smirl
2005-07-23  5:05                                 ` Antonino A. Daplas
2005-07-23 15:41                                   ` Jon Smirl
2005-07-25 16:33                                     ` James Simmons
2005-07-25 16:45                                       ` Jon Smirl

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=9e473391050624052640aa5279@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@pol.net \
    --cc=jsimmons@www.infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).