Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262977AbTEMAWA (ORCPT ); Mon, 12 May 2003 20:22:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262984AbTEMAWA (ORCPT ); Mon, 12 May 2003 20:22:00 -0400 Received: from vana.vc.cvut.cz ([147.32.240.58]:33152 "EHLO vana.vc.cvut.cz") by vger.kernel.org with ESMTP id S262977AbTEMAV4 (ORCPT ); Mon, 12 May 2003 20:21:56 -0400 Date: Tue, 13 May 2003 02:34:27 +0200 From: Petr Vandrovec To: James Simmons Cc: Linux Fbdev development list , Linux Kernel Mailing List Subject: Re: [BK FBDEV] String drawing optimizations. Message-ID: <20030513003427.GA19121@vana.vc.cvut.cz> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1188 Lines: 24 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/