From: Antonino Daplas <adaplas@pol.net>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
James Simmons <jsimmons@infradead.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: fb_imageblit semantic
Date: 17 Mar 2003 20:07:19 +0800 [thread overview]
Message-ID: <1047902787.2599.11.camel@localhost.localdomain> (raw)
In-Reply-To: <130293E23DB3@vcnet.vc.cvut.cz>
On Mon, 2003-03-17 at 18:40, Petr Vandrovec wrote:
> On 17 Mar 03 at 11:31, Geert Uytterhoeven wrote:
> > On 17 Mar 2003, Antonino Daplas wrote:
> > > As Geert said, it's not just trivial, but logical to split fb_imageblit
> > > into two.
> >
> > So, are we gonna split it? This will also make hardware acceleration support
> > more clean. E.g. most sbus drivers do color expansion in hardware, and fall
> > back to cfb_imageblit() for the logo.
> >
It's up to James, though I vote for it. And I don't think any driver
has accelerated versions of fb_imageblit for the logo, since any
performance gained is probably minimal and it will involve too much work
for something that's going to be done only once.
> > > > 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 ?
> > >
> > > Yes. You can also say that if image->depth != var->bits_per_pixel, do
> > > color expansion or reduction, whatever the case may be.
> >
> > Hmmm... Note that image->depth can be larger than 8, while the image data is
> > still 8-bit. This is an inconsistency.
I was thinking that if image->depth=8 and var->bits_per_pixel=4, then
the driver is in danger of going out of bounds when referring to the
pseudo_palette. But I forgot that the fb_show_logo() takes care of
avoiding that :-) And yes, current usage of image->depth is pretty
inconsistent and basically useless.
>
> image->depth for logo must change to 8. Or remove depth completely after
> splitting imageblit to paintchar & paintlogo, as currently depth is
> useless anyway: target format is defined by framebuffer layout, not
> by image->depth, and source format is hardwired to the code.
You're correct. If it's going to be split, image->depth becomes
redundant.
Tony
-------------------------------------------------------
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 prev parent reply other threads:[~2003-03-17 12:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 10:40 fb_imageblit semantic Petr Vandrovec
2003-03-17 12:07 ` Antonino Daplas [this message]
2003-03-17 12:18 ` Geert Uytterhoeven
2003-03-17 13:01 ` Antonino Daplas
-- 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-14 10:52 Petr Vandrovec
2003-03-16 23:00 ` Antonino Daplas
2003-03-17 10:31 ` Geert Uytterhoeven
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=1047902787.2599.11.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=vandrove@vc.cvut.cz \
/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).