All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
	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, 8 Aug 2005 13:59:50 -0400	[thread overview]
Message-ID: <9e47339105080810595158e822@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0508081831220.27739@pentafluge.infradead.org>

On 8/8/05, James Simmons <jsimmons@infradead.org> wrote:
> 
> 
> What is wrong with brekaing this patch into smaller pieces????????????
> I'm not getting a answer!!!!! As I said no giant patches that tocuh every
> driver.
> 
> > > 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.
> 
> No. fb_cursor is only used for a hardware cursor case.
> 
> > 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.
> 
> So fbops->fb_cursor will not be used at all for the console?

fbconsole check to see if fbops->fb_cursor is not null, if it is not
null it uses the hardware cursor. Otherwise it uses it's internal
softcursor implementation.

> 
> Look the patch I sent is small and doesn't interfere with many drivers. It
> does stop your desires either. Personally softcursor should go away.
> 
> 
> 
> -------------------------------------------------------
> 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
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
> 


-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
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-08-08 17: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
2005-08-08 17:35       ` James Simmons
2005-08-08 17:59         ` Jon Smirl [this message]
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=9e47339105080810595158e822@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=adaplas@hotpop.com \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.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.