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,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jon Smirl <jonsmirl@gmail.com>
Subject: Re: [RFC] Does fbdev need a cursor API for userland?
Date: Mon, 18 Oct 2004 19:05:55 +0800	[thread overview]
Message-ID: <200410181905.56602.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0410181133300.23486@waterleaf.sonytel.be>

On Monday 18 October 2004 17:35, Geert Uytterhoeven wrote:
> On Mon, 18 Oct 2004, Antonino A. Daplas wrote:
> > The restore_fb_contents/save_fb_contents cannot be done generically.  Not
> > all framebuffers have a linear format, there are some that are planar
> > such as amifb and vga16fb.  This means that we need to add per-driver
> > hooks just to save and restore the framebuffer contents.
>
> Can't we use fb_imageblit() for restore? 

fb_imageblit() is limited because it uses the pseudo_palette.  Even if
we expand the palette to 256 entries, it won't be able to handle formats >
8bpp. More than 256 is not practical. Plus, fb_imageblit is limited to
1->bpp, and 8->bpp expansion.

> Then al we need to add is a get_image() routine.

I guess if we can add get_image(), it's simple enough to write a
corresponding set_image().  Your amifb is one driver that's going to
be affected, so if you say 'yes' to the above, then let's go for a 
universal cursor implementation.

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

  reply	other threads:[~2004-10-18 10:59 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
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 [this message]
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=200410181905.56602.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=geert@linux-m68k.org \
    --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).