From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>,
James Simmons <jsimmons@infradead.org>,
Jon Smirl <jonsmirl@gmail.com>
Subject: Re: cursor maddnes and a solution
Date: Wed, 10 Aug 2005 15:50:27 +0800 [thread overview]
Message-ID: <42F9B1C3.2030201@gmail.com> (raw)
In-Reply-To: <9e4733910508092358360f8bc8@mail.gmail.com>
Jon Smirl wrote:
>
> 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.
>
I don't have anything against hardware cursor support for userspace. And
I don't even mind if we remove hardware cursor support for fbcon (I don't
see the benefit anyway). What I don't want is using fbops->fb_cursor
to support a userspace hardware cursor. In it's current incarnation
it is just wrong. Besides being a multiplexer with a 100-byte parameter,
it also requires information that are internal to fbdev only. And even if
we manage to make it work, we'll end up with a function with a multiple
personality disorder, it behaves differently when client is fbcon, and
changes behavior again when the client is userspace.
So let's keep fbops->fb_cursor for fbcon use only. Better yet, let fbcon
call soft_cursor unconditionally, remove hardware cursor from all drivers,
then overhaul fbops->fb_cursor. Or if people think this is too radical,
let's create a new cursor API and gradually phase out the old API, as
proposed in my previous post. Here's one:
struct fb_cursor_ops {
int (*cursor_move)(int x, int y);
int (*cursor_show)(int show);
int (*cursor_load_image)(u32 *image, int width, int height);
int (*cursor_load_color)(struct fb_cmap *cmap);
int (*cursor_set_size)(int width, int height);
int (*cursor_capabilities)(int set, int caps);
};
struct fb_info {
...
struct fb_cursor_ops *cursor_ops;
...
};
In cursor_load_image, we can make image to be always 32-bit truecolor and
just let the driver convert it to something the hardware can support.
In cursor_capabilities, it will either set the capabilities, or get it.
int caps may be t0o small to describe the capabilities so this can be changed.
Tony
-------------------------------------------------------
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 7:51 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
2005-08-10 7:50 ` Antonino A. Daplas [this message]
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=42F9B1C3.2030201@gmail.com \
--to=adaplas@gmail.com \
--cc=adaplas@hotpop.com \
--cc=jonsmirl@gmail.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 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).