From: Carsten Haitzler (The Rasterman) <raster@ra...> - 2011-12-26 04:35:53
On Sat, 24 Dec 2011 09:24:34 +0100 "Leufke, Philipp (INT)" <leufke@...>
aaargh. as i thought.
red, green, blue masks: 0xff, 0xff00, 0xff0000
that's the problem. and actually e17 doesnt check rgb masks - only that depth
is 32bit. :( as such e17's compositor can't work with that rgb config. it can
only work with rgb masks of:
red, green, blue masks: 0xff0000, 0xff00, 0xff
e17 COULD be made to work, but it'd add an extra copy and convert stage for
pixel fetches in software (to convert from ABGR(yours) to ARGB(evas's native
format)). this will add an extra slowdown vector. the hardware you have is
capable of ARGB perfectly well, but for some reason your x11 is not using it.
the gl compositor could be made to work too but we'd need evas to actually
support ABGR which it doesn't (so evas knows the format).
so such your only solutions are:
1. change x to use ARGB
2. disable compositing
3. provide patches to support ABGR as a source image format for all engines
(software and gl).
(nb also note that evas is adding an extra convert stage for software rendering
to display in ABGR for you so you are losing speed as a result).
> Thanks for your answer.
> Please find attached the output of xdpyinfo.
> As other HP touchpad users confirmed, the issue is only present in the
> illume-home profile and not in illume. But both result in the same xdpyinfo
> And the most important information for you: yes, composite was enabled and by
> disabling it solved the problem. I should be fine with no composite, but if
> you like to fix it, I will of course be happy and will supply debugging
> -- pml
> PS: Merry X-mas!
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...
Get latest updates about Open Source Projects, Conferences and News.