From: Antonino Daplas <adaplas@pol.net>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] Re: FBdev updates.
Date: 04 Mar 2003 05:32:33 +0800 [thread overview]
Message-ID: <1046727094.1279.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20030303203500.GA2916@vana.vc.cvut.cz>
On Tue, 2003-03-04 at 04:35, Petr Vandrovec wrote:
> My main concern now is 12x22 font... Accelerator setup
> is so costly for each separate painted character that for 8bpp
> accelerated version is even slower than unaccelerated one :-(
> (and almost twice as slow when compared with 2.4.x).
I submitted a patch to James, which he already applied to his tree, that
addresses this problem. It conglomerates the series of bitmaps into 1,
so only one fb_imageblit is necessary. It should give faster painting
than the original 2.5.x code, hopefully faster than 2.4.x code, but
slower than 8x16 painting because of the additional packing.
>
> And one (or two...) generic questions: why is not pseudo_palette
> u32* pseudo_palette, or even directly u32 pseudo_palette[17] ?
Yes, all drivers should treat the pseudo_palette as u32* anyway, so why
not change pseudo-palette from void* to u32*?
> And why we do not fill this pseudo_palette with
> i * 0x01010101U for 8bpp pseudocolor and i * 0x11111111U for 4bpp
> pseudocolor? This allowed me to remove couple of switches and tests
> from acceleration fastpaths (and from cfb_imageblit and cfb_fillrect,
> but I did not changed these two in my benchmarks below).
I also agree for a different reason. Cards with unconventional formats
(such as monochrome at 8 bpp - 0 for black , 0xff for white) will not
work with the current code.
Tony
next prev parent reply other threads:[~2003-03-03 21:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 1:09 FBdev updates James Simmons
2003-02-20 1:17 ` Jeff Garzik
2003-02-20 1:22 ` James Simmons
2003-02-20 15:02 ` Dave Jones
2003-02-20 15:07 ` James Simmons
2003-02-20 18:29 ` Petr Vandrovec
2003-02-20 19:03 ` Jurriaan
2003-02-20 19:58 ` James Simmons
2003-02-20 22:00 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-21 9:09 ` Geert Uytterhoeven
2003-02-21 10:46 ` Antonino Daplas
2003-02-21 11:02 ` Geert Uytterhoeven
2003-02-21 1:45 ` David S. Miller
2003-02-21 9:04 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-02-21 0:24 ` Antonino Daplas
2003-03-03 20:35 ` Petr Vandrovec
2003-03-03 21:25 ` Geert Uytterhoeven
2003-03-03 21:32 ` Antonino Daplas [this message]
2003-03-05 20:23 ` James Simmons
2003-03-06 1:18 ` Antonino Daplas
2003-03-04 21:29 ` Jurriaan
2003-03-04 21:46 ` Petr Vandrovec
2003-03-09 21:29 ` Petr Vandrovec
2003-03-09 22:27 ` Antonino Daplas
2003-03-09 22:54 ` Petr Vandrovec
2003-03-09 23:44 ` Antonino Daplas
2003-03-11 15:31 ` James Simmons
2003-03-05 20:22 ` James Simmons
2003-03-06 7:35 ` Sven Luther
2003-03-06 8:05 ` Antonino Daplas
2003-03-06 8:25 ` Sven Luther
2003-03-28 14:19 ` 2.5.66 fbdev performance (was Re: Re: FBdev updates) Petr Vandrovec
2003-03-28 18:50 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-20 15:10 ` FBdev updates Ivan Kokshaysky
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 20:31 [Linux-fbdev-devel] " Petr Vandrovec
2003-03-04 21:53 Petr Vandrovec
2002-06-05 16:50 fbdev updates Russell King
2002-06-05 17:21 ` [Linux-fbdev-devel] " 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=1046727094.1279.27.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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).