On Sun, Jan 25, 2009 at 9:15 PM, Jaya Kumar [off-list ref] wrote:

This is version 2 of an idea about allowing userspace to provide damage
information to drivers. Thanks to Magnus, Tomi, and others for discussion
and ideas.

...

This patch adds the ability for userspace applications to provide damage
information to the underlying driver. This is useful in scenarios where the
underlying driver can perform transfer optimizations based on knowing
exactly which framebuffer areas that were updated. This functionality is
exposed by using a simple x,y,w,h bounding box structure. Userspace is
expected to perform its damage and then perform the ioctl. The underlying
driver is free to use this information as it sees fit including ignoring it
if it chooses to. An example use case will be provided in the case of
broadsheetfb.c where the damage information is aggregated for deferred use.

Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Krzysztof Helt <redacted>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Tomi Valkeinen <redacted>
Cc: armbru@redhat.com
Cc: lethal@linux-sh.org
Cc: adaplas@gmail.com
Cc: linux-fbdev-devel@lists.sourceforge.net
Signed-off-by: Jaya Kumar <redacted>

Looking good except that the patch doesn't apply on new kernels.

Acked-by: Magnus Damm <redacted>

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword