All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: James Simmons <jsimmons@infradead.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH]: image.depth fix to accomodate monochrome cards
Date: 13 Feb 2003 07:37:54 +0800	[thread overview]
Message-ID: <1045092922.5830.136.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0302122037530.31435-100000@phoenix.infradead.org>

On Thu, 2003-02-13 at 04:50, James Simmons wrote:
> 
> > > 1.  Changed meaning of image.depth.  If image.depth == 0, it flags for
> > > color expansion, otherwise, it flags for image drawing (without color
> > > expansion).  This change is to accomodate monochrome cards so they can
> > > differentiate character drawing from logo drawing.
> > 
> > What's the status of this issue? Monochrome is still broken due to this.
> 

How about assigning fb_image.{bg_color,fg_color} to -1 if not color
expanding?  Since the pseudo_palette will not exceed 255, this should be
safe.
 
> Ug. There are a few issues left to deal with. 
> 
> 1) The cursor issue. We need to add in the cusor ioctl call for people to 
> use. Theortically there should be no issues with using soft_cursor with 
> full color images with xxfb_imageblit. I like to see dest go away in 

In order to do this, fb_imageblit has to support transparency (using a
transparency bitmask).  Userland apps will rarely have rectangular mouse
cursor pointers.  Also, it will need to support ROP's invert and copy. 
This will break fb_imageblit.  

Also, we have to double-buffer what's underneath the cursor.

Tony



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-02-12 23:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 16:16 [PATCH]: image.depth fix to accomodate monochrome cards Antonino Daplas
2003-01-07 21:06 ` Geert Uytterhoeven
2003-01-08  2:41   ` Antonino Daplas
2003-01-08  9:52     ` Geert Uytterhoeven
2003-01-08 16:25       ` Antonino Daplas
2003-01-08 16:51         ` Geert Uytterhoeven
2003-01-10 19:27     ` James Simmons
2003-01-10 19:43       ` Geert Uytterhoeven
2003-01-11  5:10         ` Antonino Daplas
2003-01-11 13:24           ` Geert Uytterhoeven
2003-01-11 13:47             ` Antonino Daplas
2003-02-05 15:03 ` Geert Uytterhoeven
2003-02-05  7:14   ` Antonino Daplas
2003-02-12 20:50   ` James Simmons
2003-02-12 23:37     ` Antonino Daplas [this message]
2003-02-13  9:27       ` Geert Uytterhoeven

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=1045092922.5830.136.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@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.