linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>,
	Jon Smirl <jonsmirl@gmail.com>
Subject: Re: [RFC] Does fbdev need a cursor API for userland?
Date: Tue, 19 Oct 2004 16:55:59 +0800	[thread overview]
Message-ID: <200410191655.59426.adaplas@hotpop.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0410190958340.13789@waterleaf.sonytel.be>

On Tuesday 19 October 2004 16:01, Geert Uytterhoeven wrote:
> On Tue, 19 Oct 2004, Antonino A. Daplas wrote:
> > On Tuesday 19 October 2004 05:00, Geert Uytterhoeven wrote:
> > > On Tue, 19 Oct 2004, Antonino A. Daplas wrote:
> > > > On Monday 18 October 2004 20:01, Geert Uytterhoeven wrote:
> > > > > On Mon, 18 Oct 2004, Antonino A. Daplas wrote:
> > > > > > On Monday 18 October 2004 17:35, Geert Uytterhoeven wrote:
> > > > > > > On Mon, 18 Oct 2004, Antonino A. Daplas wrote:
> > >
> > > I didn't intend it to do conversions. 32-bit ARGB would be used for
> > > truecolor visuals only.
> > >
> > > > Isn't it much simpler to just have a set_image() where the source
> > > > block is in the same format as the framebuffer so it doesn't have to
> > > > do format conversions?
> > >
> > > Yes it is.
> > >
> > > The fb_imageblit() approach is just more generic, and could (in theory)
> > > be used from user space as well, allowing applications to not have to
> > > care about the actual frame buffer format anymore. All they have to
> > > handle is 1-bit monochrome, 8-bit pseudocolor and 32-bit ARGB
> > > truecolor.
> >
> > We still have to do conversions, say from 32-bit ARGB to RGB565.  And
> > this is just for truecolor.
>
> Indeed.
>
> > How about directcolor?
>
> You're right. And currently directcolor is treated like pseudocolor w.r.t.
> the console and the penguin logo.
>
> Hmm, bad idea, at least for saving/restore for the cursor.

Well, your proposal sounds useful though. We can still expand imageblit so it has
these additional functions:

32-bit ARGB truecolor ->any truecolor format
32-bit ARGB directcolor-> any directcolor format
8-bit pseudocolor -> all formats <= 8 bpp && !directcolor && !truecolor 

(First and second is easy to add. The third may be a bit tricky because
it conflicts with already existing code for the penguin, but I think it's
fixable. The logo code in fbmem.c and color_imageblit need to be rewritten.)

I think with the above we cover everything for packed-pixel formats.

Then for the cursor (if people still want it), we just add get_image_raw()
and set_image_raw() hooks which gets/sets the contents in native framebuffer
format.

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-19  8:49 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
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 [this message]
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=200410191655.59426.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).