From: Jon Smirl <jonsmirl@gmail.com>
To: adaplas@pol.net
Cc: linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@www.infradead.org>
Subject: Re: PATCH: move soft_cursor into fbconsole
Date: Sat, 23 Jul 2005 11:41:23 -0400 [thread overview]
Message-ID: <9e473391050723084153d29566@mail.gmail.com> (raw)
In-Reply-To: <200507231305.59225.adaplas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]
This not currently resolved.
From user space we can have two interfaces
1) the current ioctl one
2) the new stuff in sysfs. If the hardware cursor is there you get a sysfs
attribute named cursor. write x,y to it to move the cursor around. I'll add
the sysfs support as soon as we decide on the interface.
I'm still at OLS. Missed seeing both of you at KS. fbdev was discussed and
Linus went with Benh's proposal to move the modesetting API to user space.
Obviously this will have a lot of impact on fbdev.
On 7/23/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
>
> On Saturday 02 July 2005 08:56, Jon Smirl wrote:
> > Another way to think of this, let's make another member variable
> > .fb_hwcursor. When the driver has a hardware cusor is sets
> > .fb_hwcursor. If you want to use the software cursor use the exisiting
> > .fb_cursor.
> >
> > If you think about it every driver is going to have the exact same
> > assignment .fb_cursor = soft_cursor. If every driver is going to have
> > exactly the same assignment, why do we need the variable?
> >
> > It's the existence of the hardware cursor that varies from driver to
> > driver, that's the one we need the variable for.
>
> Is this resolved? I tend to agree with Jon. Let's just remove all
> references to soft_cursor from all drivers, and let fbcon_cursor() fall
> back
> to soft_cursor when xxxfb_cursor() is absent. It is a lot cleaner and
> saner
> this way, and although it touches all drivers, it is a singe logical
> change,
> so it's acceptable.
>
> Also, I think it might be preferable to have 2 cursor hooks, one
> is fbcon-specific, and the other is for use only in userspace, which needs
> to be more comprehensive. Or if a single but comprehensive cursor API is
> preferred, then we just adapt fbcon_cursor to use the more powerful
> cursor API.
>
> So, anyone want to propose a cursor API for fbdev, that is both usable by
> fbcon and userspace?
>
> Tony
>
>
>
--
Jon Smirl
jonsmirl@gmail.com
[-- Attachment #2: Type: text/html, Size: 2474 bytes --]
next prev parent reply other threads:[~2005-07-23 15:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 4:57 PATCH: move soft_cursor into fbconsole Jon Smirl
2005-06-11 6:15 ` James Simmons
2005-06-11 13:10 ` Jon Smirl
2005-06-11 13:23 ` Jon Smirl
2005-06-11 20:35 ` Geert Uytterhoeven
2005-06-11 22:01 ` Jon Smirl
2005-06-12 7:43 ` Geert Uytterhoeven
2005-06-16 1:34 ` Jon Smirl
2005-06-16 3:11 ` Antonino A. Daplas
2005-06-16 3:37 ` Jon Smirl
2005-06-21 0:07 ` James Simmons
2005-06-21 0:31 ` Jon Smirl
2005-06-24 0:09 ` James Simmons
2005-06-24 12:26 ` Jon Smirl
2005-06-24 16:17 ` James Simmons
2005-06-24 16:27 ` Jon Smirl
2005-06-24 17:13 ` James Simmons
2005-06-24 17:25 ` Jon Smirl
2005-07-01 23:32 ` James Simmons
2005-07-01 23:52 ` Sylvain Meyer
2005-07-06 23:28 ` James Simmons
2005-07-02 0:28 ` Jon Smirl
2005-07-02 0:56 ` Jon Smirl
2005-07-23 5:05 ` Antonino A. Daplas
2005-07-23 15:41 ` Jon Smirl [this message]
2005-07-25 16:33 ` James Simmons
2005-07-25 16:45 ` Jon Smirl
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=9e473391050723084153d29566@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@pol.net \
--cc=jsimmons@www.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.