From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Move softcursor out of fbdev to fbcon
Date: Thu, 28 Jul 2005 02:50:39 +0800 [thread overview]
Message-ID: <42E7D77F.6020005@gmail.com> (raw)
In-Reply-To: <9e473391050727073269e33a44@mail.gmail.com>
Jon Smirl wrote:
> On 7/27/05, Antonino A. Daplas <adaplas@gmail.com> 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()
>
> What does start/stop do?
Wrong choice of words, this is just an example. But start() should tell
the driver that the cursor is going to be used, and perhaps do some locking (so
another app does not try to grab the device). It can also return the
capabilities of the cursor: maximum dimensions, color depth of image,
caps such as alpha, transparency, etc. stop() will release the cursor.
>
>> 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.
>
> It has always bugged me that there was no real interface between
> fbconsole and fbdev. For example I tried to write a wrapper for DRM so
> that fbconsole could use DRM for accelerated console. But fbconsole is
> so tied into the fbdev data structures writing the wrapper required me
> to build most of an fbdev driver. I shouldn't need to do that,
> fbconsole should not be poking at fb_info, it should use an API for
> making changes.
Yes. I think I'm planning to do that in small steps. I'm thinking first of
separating all fbcon-specific fields and place them in another structure,
ie, fbcon_info. This struct will be registered separately from fb_info,
and only if fbcon is enabled.
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-07-27 18:50 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 [this message]
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
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=42E7D77F.6020005@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.