From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Helt <krzysztof.h1@poczta.fm>
Cc: spock@gentoo.org, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] fbdev: fix fillrect for 24bpp modes
Date: Fri, 17 Apr 2009 11:50:48 -0700 [thread overview]
Message-ID: <20090417115048.0c5ca35d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090417183617.ed7553cd.krzysztof.h1@poczta.fm>
On Fri, 17 Apr 2009 18:36:17 +0200
Krzysztof Helt <krzysztof.h1@poczta.fm> wrote:
> On Mon, 13 Apr 2009 19:09:54 +0200
> Michal Januszewski <spock@gentoo.org> wrote:
>
> ...
>
> The r is simply dst_idx / bits. Most compilers will optimize it away into
> a simple shift because the bits has only one bit set (it is number of bits in a long variable, ie. 32 or 64).
>
> > + pat = pat << ((left*r) % bpp) | pat >> ((right*r) % bpp);
> >
>
> If the r = (dst_idx / bits) it is number of long words. The shift by ((left*r) % bpp) does
> not make much sense (try left = 3 and r = 24 words - it is always zero but should be 3).
> It is even worse if a line is padded so line's length modulo bpp is not
> zero it does not work. A colorful pattern is produced after the "mtest" text.
>
> A dst_idx offset is not taken into account (it could be non-zero only for depths < 8 bits).
>
OK, thanks for checking.
Michael, I'll await a version 2 on this patch. It looks like something
we want in 2.6.30.
next prev parent reply other threads:[~2009-04-17 18:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 17:09 [PATCH] fbdev: fix fillrect for 24bpp modes Michal Januszewski
2009-04-17 16:36 ` [Linux-fbdev-devel] " Krzysztof Helt
2009-04-17 18:50 ` Andrew Morton [this message]
2009-04-18 18:52 ` [PATCH v2] " Michal Januszewski
2009-04-20 23:07 ` Andrew Morton
2009-05-01 21:47 ` [PATCH v3] " Michal Januszewski
2009-04-21 5:10 ` [PATCH v2] " Krzysztof Helt
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=20090417115048.0c5ca35d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spock@gentoo.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).