linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Jon Smirl <jonsmirl@gmail.com>
Subject: Re: [RFC] Does fbdev need a cursor API for userland?
Date: Mon, 18 Oct 2004 09:20:39 +0800	[thread overview]
Message-ID: <200410180920.39170.adaplas@hotpop.com> (raw)
In-Reply-To: <9e4733910410171525543c1992@mail.gmail.com>

On Monday 18 October 2004 06:25, Jon Smirl wrote:
> On Sun, 17 Oct 2004 23:47:15 +0800, Antonino A. Daplas
>
> <adaplas@hotpop.com> wrote:
> > IMO, I believe that the cursor ioctl should just be removed :-)
>
> The merged fbdev/DRM needs hardware cursor support in fbdev but it

A kernel-to-kernel interface to the hardware cursor is easier to implement since
we always trust kernel data, so that is not much of a problem. The problematic
area is the generic, non-fbcon specific cursor implementation, and exporting
the interface to userspace. All are doable of course, and I'm willing to code it
if people want it.

> doesn't need the fbdev cursor IOCTL. Moving cursor support to fbcon
> won't work either. Implementing cursor support in merged fbdev/DRM
> probably means a modified API since we have to deal with multiple
> heads.
>
> Are there cards still out there with no hardware cursor support?

All hardware, except for the platform ones, probably have hardware cursor
support, but most are unimplemented.  In 2.6, only i810fb and rivafb have a 
hardware cursor implementation.  The rest, tdfxfb, imsttfb, mach64fb, neofb,
etc are broken and the code is commented out, so they use softcursor
instead.  There is a patch for mach64 though that fixes the hardware cursor
implementation, but it's not in mainline yet.
 
> How many apps use the user space fbdev interface?

The standard user fbdev interface are used by a lot of applications.
However, the cursor ioctl interface is new in 2.6, and since it's broken, I
doubt if any major apps use it.

Tony




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

  parent reply	other threads:[~2004-10-18  1:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 15:47 [RFC] Does fbdev need a cursor API for userland? Antonino A. Daplas
2004-10-17 17:18 ` Zachary Smith
2004-10-17 21:51   ` Antonino A. Daplas
2004-10-17 22:25     ` Jon Smirl
2004-10-17 23:49       ` Zachary Smith
2004-10-18  1:18         ` Antonino A. Daplas
2004-10-18  1:20       ` Antonino A. Daplas [this message]
2004-10-18  2:46         ` Jon Smirl
2004-10-18  6:47           ` Antonino A. Daplas
2004-10-18  9:35             ` Geert Uytterhoeven
2004-10-18 11:05               ` Antonino A. Daplas
2004-10-18 12:01                 ` Geert Uytterhoeven
2004-10-18 12:10                   ` Geert Uytterhoeven
2004-10-18 20:56                   ` Antonino A. Daplas
2004-10-18 21:00                     ` Geert Uytterhoeven
2004-10-18 21:34                       ` Antonino A. Daplas
2004-10-19  8:01                         ` Geert Uytterhoeven
2004-10-19  8:55                           ` Antonino A. Daplas
2004-10-18  7:06           ` 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=200410180920.39170.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=jonsmirl@gmail.com \
    --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).