From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fb_imageblit semantic
Date: Fri, 14 Mar 2003 11:52:29 +0100 [thread overview]
Message-ID: <12BAC7B62B6D@vcnet.vc.cvut.cz> (raw)
On 14 Mar 03 at 11:40, Geert Uytterhoeven wrote:
> On Fri, 14 Mar 2003, Petr Vandrovec wrote:
> > On 14 Mar 03 at 10:22, Geert Uytterhoeven wrote:
> > > On Thu, 13 Mar 2003, Petr Vandrovec wrote:
> > > > Why do you pass image.depth == 16 (or 24 or 32) to fb_imageblit
> > > > when logo image is in reality always 8bpp, as quick look at
> > > > cfb_imageblit revealed?
> > >
> > > Should indeed be 8.
> > >
> > > > Should I just assume that image.depth == 1 means that data are
> > > > 1bpp with fgcol/bgcol valid, and all other depths mean 8bpp
> > > > input?
> > >
> > > This was changed from 1 to 0 in James' latest tree.
> >
> > WTF? Color depth 0 means that whole picture is single-color, and
> > imageblit degenerates to rectfill in such case. Please, either
> > use 'depth' as source image color depth, or do not name it depth.
>
> It's 0 (expand [bf]gcol) to differentiate from 1 (copy monochrome).
>
> Splitting imageblit into separate routines for both operations would be
> trivial, though.
There is no such thing as copy monochrome if target is not monochrome,
you have to put palette somewhere. If you'll look at cfb_imageblit,
you'll find that there is already defined way to do that: code uses
artifically created 256 entry pseudopalette... If target is monochrome,
it just copies data. If target is not monochrome, it has somehow expand
data to fit to screen format. Nothing differs between font painting
and copying 1bpp bitmap to Xbpp display.
OK, so rule is that if depth=0, input is 1bpp with palette in bgcol/fgcol,
while if depth != 0, then palette is in info->pseudo_palette ?
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
next reply other threads:[~2003-03-14 10:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:52 Petr Vandrovec [this message]
2003-03-16 23:00 ` fb_imageblit semantic Antonino Daplas
2003-03-17 10:31 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 12:25 Petr Vandrovec
2003-03-17 12:40 ` Geert Uytterhoeven
2003-03-17 13:02 ` Antonino Daplas
2003-03-17 13:47 ` Geert Uytterhoeven
2003-03-17 14:24 ` Antonino Daplas
2003-03-17 14:46 ` Geert Uytterhoeven
2003-03-17 10:40 Petr Vandrovec
2003-03-17 12:07 ` Antonino Daplas
2003-03-17 12:18 ` Geert Uytterhoeven
2003-03-17 13:01 ` Antonino Daplas
2003-03-14 10:18 Petr Vandrovec
2003-03-14 10:40 ` Geert Uytterhoeven
2003-02-20 1:09 FBdev updates James Simmons
2003-02-20 15:02 ` Dave Jones
2003-02-20 18:29 ` Petr Vandrovec
2003-02-21 0:24 ` Antonino Daplas
2003-03-03 20:35 ` [Linux-fbdev-devel] " Petr Vandrovec
2003-03-04 21:29 ` Jurriaan
2003-03-09 21:29 ` Petr Vandrovec
2003-03-09 22:27 ` Antonino Daplas
2003-03-09 22:54 ` Petr Vandrovec
2003-03-13 22:23 ` fb_imageblit semantic Petr Vandrovec
2003-03-14 9:22 ` 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=12BAC7B62B6D@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--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 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).