linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK FBDEV] String drawing optimizations.
Date: Tue, 13 May 2003 02:34:27 +0200	[thread overview]
Message-ID: <20030513003427.GA19121@vana.vc.cvut.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0305130049520.14641-100000@phoenix.infradead.org>

On Tue, May 13, 2003 at 01:02:40AM +0100, James Simmons wrote:
> 
> Please test. The pixmap code in the framebuffer layer was designed to 
> align the font data. For some hardware it is required that each scanline 
> end on a byte boundary but for some  it was to be 32 bit aligned. So the
> solution was to take the image data and padded it to what the hardware 
> needs. At present it does this by coping on byte at a time. This is just 
> plain awful. So this patch copies data a whole scanline at a time. It is
> a big performance boost. Please test before I send it to Linus. Thank 
> you.

What about getting rid of one-char putc, implementing it in terms of
putcs? I'm doing it in matroxfb patches, and nobody complained yet, and
with current length of {fbcon,accel}_putc{s,} I was not able to find
measurable speed difference between putc and putc through putcs variants.
						Thanks,
							Petr Vandrovec
							vandrove@vc.cvut.cz



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

  reply	other threads:[~2003-05-13  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  0:02 [BK FBDEV] String drawing optimizations James Simmons
2003-05-13  0:34 ` Petr Vandrovec [this message]
2003-05-15 20:27   ` James Simmons
2003-05-16  8:24     ` 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=20030513003427.GA19121@vana.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).