From: Jon Smirl <jonsmirl@gmail.com>
To: Andrey Volkov <avolkov@varma-el.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
"Antonino A. Daplas" <adaplas@gmail.com>,
James Simmons <jsimmons@infradead.org>
Subject: Re: cursor maddnes and a solution
Date: Wed, 10 Aug 2005 11:51:24 -0400 [thread overview]
Message-ID: <9e47339105081008517561bfbc@mail.gmail.com> (raw)
In-Reply-To: <42FA1F55.5010801@varma-el.com>
On 8/10/05, Andrey Volkov <avolkov@varma-el.com> wrote:
>
>
> Jon Smirl wrote:
> > On 8/10/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
> >
> >>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);
> >>};
> >
> >
> > Doen't fb already support an image format with embedded color map? Can
> > we use it and merge:
> >
> >> int (*cursor_load_image)(u32 *image, int width, int height);
> >> int (*cursor_load_color)(struct fb_cmap *cmap);
> >
> >
> > The size can also be computed from the image so the size call can be eliminated.
> >
> You are omit hwd cursor size problem - very few (possible no one)
> graphics chips could support cursor with any size. Usually they support
> 32x32/64x64 pixels cursors only. For kernel fb its have not meaning,
> 'cause we always could fallback to the soft_cursor (in the fbcon or
> directly in a driver), BUT what to do with such crazy user who will wish
> to use, ex. 100x100 pix cursor in user space?
You would just get an error back if the hardware cursor doesn't
support the big size. Your user space app would then have to implement
a fallback software one. You always have to implement the software
fallback since not all hardware may expose the cursor.
You can't implement the software cursor for user space in the kernel
because there is no way to synchronize it with user space drawing. I
think the better solution is for user space apps to handle it than to
try and build a synchronization system into fbdev.
If you are writing X apps you don't have to deal with any of this, X
handles it all for you.
--
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 15: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
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 [this message]
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=9e47339105081008517561bfbc@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@gmail.com \
--cc=avolkov@varma-el.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).