All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: James Simmons <jsimmons@www.infradead.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
	"Antonino A. Daplas" <adaplas@hotpop.com>,
	James Simmons <jsimmons@pentafluge.infradead.org>
Subject: Re: PATCH: move soft_cursor into fbconsole
Date: Sat, 11 Jun 2005 09:23:17 -0400	[thread overview]
Message-ID: <9e473391050611062323284c4e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0506110711100.24250@pentafluge.infradead.org>

On 6/11/05, James Simmons <jsimmons@www.infradead.org> wrote:
> 
> Ug no. I see in the future more drivers using hardware cursors instead.
> We would be carry around extra software cursor code in the the framebuffer
> console all the time. We need to properly fix the cursor code. Unfortunely
> that will take more work. In the mean time please encourage people to
> support hardware cursors. Even crappy cards have hardware cursors most of
> the time.

Also, I didn't delete the fb_cursor field. I just removed all of the
assignments of .fb_cursor = soft_cursor. The field is still there and
defaulting to null, except in the three drivers with hardware cursors
where it is set.

For a driver to implement software cursors it has to know the location
of the scanout buffer, scanbuffer format, etc. I not sure if all of
this is always know for user space apps. The hardware cursor doesn't
need as much info about the framebuffer.

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r 

  parent reply	other threads:[~2005-06-11 13:23 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 [this message]
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
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=9e473391050611062323284c4e@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=jsimmons@pentafluge.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.