From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Andrey Volkov <avolkov@varma-el.com>,
linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@infradead.org>
Subject: Re: cursor maddnes and a solution
Date: Thu, 11 Aug 2005 00:07:46 +0800 [thread overview]
Message-ID: <42FA2652.1060308@gmail.com> (raw)
In-Reply-To: <9e47339105081008517561bfbc@mail.gmail.com>
Jon Smirl wrote:
> 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);
Yes, we can do that.
>>>
>>> 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?
>
If cursor_capabilities() is called, it should return the maximum
dimensions supported by the hardware.
Meaning, we have to change it to:
int (*cursor_capabilities)(int set, struct fb_cursor_caps *caps);
so it passes struct fb_cursor_caps *caps instead of int caps.
Of course, if user is so crazy that he/she insists on using a 100x100 cursor
image, the kernel should return an error and, as Jon said, fallback to
a software implementation
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 16:08 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
2005-08-10 16:07 ` Antonino A. Daplas [this message]
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=42FA2652.1060308@gmail.com \
--to=adaplas@gmail.com \
--cc=avolkov@varma-el.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).