All of lore.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: RFC: bitmap line alignment
Date: Fri, 25 Nov 2005 13:16:35 +0100	[thread overview]
Message-ID: <438700A3.3070503@t-online.de> (raw)

Hi everybody

I learned the hard way that image->width*image->height is not equal to the
number of bits consumed by the image bitmap. Every single line of bits is
aligned to a byte boundary.

Wouldn´t it be much more efficient to align every line to an u32 boundary?
Despite the obvious advantages of aligned cpu access to large arrays it
would also help to simplify the code for at least the cyberblade 
acceleration
engine.

The cyberblade always requires 32 bit quantities, so if the width of the 
image
is eg. 33, I have to feed _two_ u32 to it for every pixel line. Is the 
same true
for other acceleration engines?

I have not read the code of most of the framebuffer drivers, but I know 
that
a lot of them do not use accelerated imageblits. Those that do provide 
their own
functions would need to be adapted, as well as the cfb_imageblit 
function ...

Comments, please.

cu,
 Knut


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

             reply	other threads:[~2005-11-25 12:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-25 12:16 Knut Petersen [this message]
2005-11-25 12:36 ` RFC: bitmap line alignment Antonino A. Daplas
2005-11-25 14:10   ` Knut Petersen

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=438700A3.3070503@t-online.de \
    --to=knut_petersen@t-online.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.