From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@hotpop.com>
Cc: James Simmons <jsimmons@infradead.org>
Subject: Re: cursor maddnes and a solution
Date: Wed, 10 Aug 2005 02:58:48 -0400 [thread overview]
Message-ID: <9e4733910508092358360f8bc8@mail.gmail.com> (raw)
In-Reply-To: <42F99B5E.1070309@gmail.com>
You have a cursor and a caret. The caret is used for typing text and
the cursor follows the mouse.
Next you are are either in text or graphics mode. How you generate the
caret/cursor is quite different in the two modes. User space doesn't
care about text mode so you can handle it in fbconsole. I'm not sure
how gdm generates a mouse cursor in text mode. Since it is fairly easy
to generate the cursor/caret in software in text mode, I don't know it
if it worth the effort to try and use hardware support.
In graphics mode user space will use the hardware mouse cursor if it
is available. I believe there are a few chips that support multiple
sprites, one could be used for the cursor and one for the caret. This
isn't common so the caret is almost always software generated.
The hardware mouse cursor is relevant in graphics mode because you may
not be able to generate screens in real time. If you can't the
software mouse cursor lags and may become unusable. Hardware mouse
cursor eliminates this problem.
Graphical fbconsole doesn't have a lag problem so it may just want to
software generate.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-10 6:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 0:17 cursor maddnes and a solution James Simmons
2005-08-10 6:14 ` Antonino A. Daplas
2005-08-10 6:58 ` Jon Smirl [this message]
2005-08-10 7:50 ` Antonino A. Daplas
2005-08-10 8:06 ` Antonino A. Daplas
2005-08-10 13:25 ` Jon Smirl
2005-08-10 15:37 ` Andrey Volkov
2005-08-10 15:51 ` Jon Smirl
2005-08-10 16:07 ` Antonino A. Daplas
2005-08-10 16:18 ` Andrey Volkov
2005-08-10 16:33 ` Antonino A. Daplas
2005-08-11 22:40 ` James Simmons
2005-08-11 22:37 ` James Simmons
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=9e4733910508092358360f8bc8@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@hotpop.com \
--cc=jsimmons@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.