Compositor for eink device

[Pekka Paalanen]

On Tue, 11 Jun 2013 12:37:33 +0200
Claudius Marpa Heine <claudius.marpa.heine at student.uni-augsburg.de>
wrote:

> Am Dienstag, den 11.06.2013, 13:16 +0300 schrieb Pekka Paalanen:
> > On Tue, 11 Jun 2013 10:56:49 +0100
> > martin brook <martin.brook100 at googlemail.com> wrote:
> > 
> > > Guys Hi,
> > > 
> > > An interesting area which I've done some work on with a kobo touch, some
> > > useful links at
> > > 
> > > https://wiki.merproject.org/wiki/Community_Workspace/kobo
> > 
> > Ok, only static pseudocolor, of course. Hopefully that matches PIXMAN_g8
> > format and pixman does the conversion automatically and without too
> > much hit.
> > 
> > The current pixman renderer in Weston is written for ARGB
> > compositing of client provided images. It is wasteful to first
> > composite in ARGB and then convert to grayscale, so if that needs
> > optimizing, you may need to:
> > - convert incoming buffers to grayscale and maintain a copy
> > - modify the pixman renderer to composite in grayscale+alpha, if
> >   possible
> > - add a grayscale pixel format to wl_shm protocol (I have planned on
> >   adding more formats anyway)
> > - modifying clients to use the grayscale format
> > 
> > But I think it is possible to start with the pixman renderer as is, and
> > convert to grayscale when copying to the fb.
> 
> Not sure if that helps, but someone successfully converted the content
> of the framebuffer to RGB:
> http://www.chauveau-central.net/pub/KoboTouch/

That seems to be a different color format than in the Mer wiki link.
The same caveats may still apply. In any case, you have the chance to
convert to the right format when copying from the shadow to the real fb.

Thanks,
pq