All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Move softcursor out of fbdev to fbcon
Date: Thu, 28 Jul 2005 10:12:16 +0800	[thread overview]
Message-ID: <42E83F00.2060403@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0507272302500.3729@pentafluge.infradead.org>

James Simmons wrote:
>> The changelog says it all. This is a modification of Jon's patch, but
>> I have moved softcursor.c to the console directory.  Also I removed
>> the "select FB_SOFTCURSOR" from video/Kconfig and made the compilation
>> of softcursor unconditional, if framebuffer console is enabled.
>>
>> I don't think the fb_cursor hook is usable by other programs, so we
>> should just restrict this hook for fbcon use only.  For userspace cursor
>> support, we need a new one.  But instead of one function, I believe
>> it's better to provide several.  Ie, something like below:
>>
>> fbcursor_show()         
>> fbcursor_move()
>> fbcursor_loadimage()
>> fbcursor_loadpalette()
>> fbcursor_start()
>> fbcursor_stop() 
>>
>> No need to pass all variables to just, say, move the cursor to x,y.
>>
>> And the next step is to eliminate all fbcon-specific fields from
>> fb_info to another structure, such as fb_imageblit, fb_fillrect,
>> fb_cursor, fb_copyarea.  We'll have a smaller kernel size for
>> if fbcon is not enabled.
>>
>> Comments?
> 
> Its way to big and gross. Please keep it simple!!!!!! 

Actually, it's the other way around. Functions should do just one thing.
In contrast, our fb_cursor() function is doing all of the above
and more.  Breaking up fb_cursor() into several may have a bit of a
memory overhead, but the end result is more efficient code.  Do you really
want the user app to pass the quite large struct fb_cursor to the kernel just
to move the cursor?  Or is it better just to pass two integers, x and y?

Remember, what I'm proposing is an API that is usable by userspace and other
kernel modules, and only if the driver supports a hardware cursor.  The current
fb_cursor() used by fbcon can remain, if that is what you want. Because
fb_cursor() was designed for fbcon (as with all of the fb_* drawing functions),
they can never be used by other modules without a lot of pain.

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

      reply	other threads:[~2005-07-28  2:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  7:49 Move softcursor out of fbdev to fbcon Antonino A. Daplas
2005-07-27 14:32 ` Jon Smirl
2005-07-27 18:50   ` Antonino A. Daplas
2005-07-27 19:05     ` Jon Smirl
2005-07-27 22:17     ` James Simmons
2005-07-28  0:42       ` Jon Smirl
2005-07-28  2:12       ` Antonino A. Daplas
2005-07-28 18:39         ` James Simmons
2005-07-28 22:22           ` Antonino A. Daplas
2005-07-27 22:04 ` James Simmons
2005-07-28  2:12   ` Antonino A. Daplas [this message]

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=42E83F00.2060403@gmail.com \
    --to=adaplas@gmail.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 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.