LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
<linux-fbdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] video: fbdev: fix sys_copyarea
Date: Fri, 30 Jan 2015 08:49:30 +0000 [thread overview]
Message-ID: <yw1xh9v8bqlh.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <54CB38B6.3010202@ti.com> (Tomi Valkeinen's message of "Fri, 30 Jan 2015 09:54:30 +0200")
Tomi Valkeinen <tomi.valkeinen@ti.com> writes:
> On 22/01/15 03:19, Mans Rullgard wrote:
>> The sys_copyarea() function performs the same operation as
>> cfb_copyarea() but using normal memory access instead of I/O
>> accessors. Since the introduction of sys_copyarea(), there
>> have been two fixes to cfb_copyarea():
>>
>> - 00a9d699 ("framebuffer: fix cfb_copyarea")
>> - 5b789da8 ("framebuffer: fix screen corruption when copying")
>>
>> This patch incorporates the fixes into sys_copyarea() as well.
>>
>> Signed-off-by: Mans Rullgard <mans@mansr.com>
>> ---
>> Changed in v2:
>> - Fixed wrong first/last calculation in bitcpy_rev()
>> ---
>> drivers/video/fbdev/core/syscopyarea.c | 137 ++++++++++++++++-----------------
>> 1 file changed, 65 insertions(+), 72 deletions(-)
>
> Thanks, queued for 3.20.
>
> This makes me wonder, though, if the sys and cfb versions could be
> somehow combined...
I would have done it by #including a common template with different
macro definitions for the memory access operations.
--
Måns Rullgård
mans@mansr.com
prev parent reply other threads:[~2015-01-30 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 1:19 Mans Rullgard
2015-01-30 7:54 ` Tomi Valkeinen
2015-01-30 8:49 ` Måns Rullgård [this message]
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=yw1xh9v8bqlh.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
--subject='Re: [PATCH v2] video: fbdev: fix sys_copyarea' \
/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
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).