From: "Antonino A. Daplas" <adaplas@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Antonino A. Daplas" <adaplas@hotpop.com>
Subject: Re: [PATCH] Don't allow softcursor use from userland
Date: Mon, 08 Aug 2005 08:59:33 +0800 [thread overview]
Message-ID: <42F6AE75.6090409@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508080013400.12912@pentafluge.infradead.org>
James Simmons wrote:
>> James Simmons wrote:
>>
>>> This patch forbids the cursor use from userland. The reason is that the
>>> cursor area could be altered by a another process and the current system
>>> doesn't handle syncing those updates.
>>>
>>>
>> I don't really like this change. I prefer Jon's proposal of setting
>> fbops->fb_cursor = NULL and moving softcursor.c to drivers/video/console.
>> This will slash > 200 lines of source code and several bytes from the kernel
>> image size. Plus it's cleaner.
>>
>
> One change at a time. If you want to properly do cursor in fbcon then just
> moving softcursor there is not the answer. What if you have a driver that
>
See the patch again, there's only one logical change. And the intent of the
patch was never to support userspace cursor.
> has software image blit and hardware fillrect. You want to have fbcon use
>
Then the driver sets fbops->fb_cursor with its own version that does
fillrect instead of imageblit.
I think you're still trying to overload fbops->fb_cursor. These drawing
functions in info->fbops (fb_imageblit, fb_fillrect, fb_copyarea and
fb_cursor) are for fbcon use _only_. They cannot be used in userspace
because of the inherent limitations of the code, and it depends on fields
that are internal to fbdev/fbcon (ie pseudo_palette). And even if you make it
work, I doubt it will be efficient code. Remember that the fbcon hooks were
written in such a way so that we can have a very fast console, but it
sacrifices userspace compatibility.
If you want to add userspace support for hardware cursors then you have to
create another API. If you don't want another API, then forget about userspace
support. Overloading fbops->fb_cursor is not the answer.
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-08 0:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 2:34 [PATCH] Don't allow softcursor use from userland James Simmons
2005-08-07 4:27 ` Andrew Morton
2005-08-07 4:41 ` Jon Smirl
2005-08-07 23:25 ` James Simmons
2005-08-07 23:19 ` James Simmons
2005-08-07 10:35 ` Antonino A. Daplas
2005-08-07 23:17 ` James Simmons
2005-08-08 0:59 ` Antonino A. Daplas [this message]
2005-08-08 17:35 ` James Simmons
2005-08-08 17:59 ` Jon Smirl
2005-08-08 18:16 ` James Simmons
2005-08-08 23:56 ` Antonino A. Daplas
2005-08-09 0:10 ` 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=42F6AE75.6090409@gmail.com \
--to=adaplas@gmail.com \
--cc=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--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.