mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: James Simmons <jsimmons@transvirtual.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	linuxconsole-dev@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, geert@linux-m68k.org
Subject: Re: [PATCH] Hooks for new fbdev api
Date: Thu, 29 Nov 2001 18:58:24 MET-1	[thread overview]
Message-ID: <A9484F0657A@vcnet.vc.cvut.cz> (raw)

On 29 Nov 01 at 9:35, James Simmons wrote:
> +struct fbcursor {
> +   __u16 set;      /* what to set */
> +   __u16 enable;/* cursor on/off */
> +   struct fbcurpos pos;/* cursor position */
> +   struct fbcurpos hot;/* cursor hot spot */
> +   struct fb_cmap cmap;/* color map info */

>From what you wrote I assume that cmap.start must be 0 and cmap.len
some length, and it must be always set, as otherwise it is impossible
to guess image/mask depth from it.

> +   struct fbcurpos size;/* cursor bit map size */
> +   char *image;/* cursor image bits */
> +   char *mask;/* cursor mask bits */

And maybe it is better to go with Geert idea? Remove mask, and
make image just really use cmap - if cmap entry is 100% transparent,
it is like that bit(mask) == 1, and add one more field for inverted
cmap entry. As no driver can use image/mask immediately anyway, there
is no big problem.

I hope that mask/image format is going to be specified somewhere
more exactly - like whether each image/mask line consist of 
non-fractional number of bytes, what happens if cmap has 8 entries 
and other legal, but hard to implement, features...
                                                    Petr Vandrovec
                                                    vandrove@vc.cvut.cz
                                                    

             reply	other threads:[~2001-11-29 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-29 18:58 Petr Vandrovec [this message]
2001-11-29 18:08 ` James Simmons
2001-11-30  8:44   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2001-11-28 18:50 James Simmons
2001-11-29  7:52 ` Geert Uytterhoeven
2001-11-29 17:35   ` 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=A9484F0657A@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@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

all inboxes | Powered by JetHome®