We would like to set winmgr.conf / display / plane / elg-conifig
to a value corresponding to 16 bits of bit-depth in order to avoid
flicker on an i.mx35-based system.

Per the documentation and your previous response we were
running io-winmgr -sysres (after another instance of io-winmgr was already running) but the config values reported do
not appear to be correct.  We judged that based on the presence
of flicker.

We managed to obtain correct 16-bit configuration values by running io-winmgr -sysres while no other instance of io-
winmgr was running in the system but in this case the io-winmgr process never terminated, unless
we sent it a signal.

Also, when starting io-winmgr -sysres in the background and looking
at its state with the pidin command, io-winmgr was always in the
READY state and the hogs utility reported io-winmgr as using
85% of the CPU (with another 13% used by io-pkt even though
no  network communication was going on in the system).

The last few lines output by io-winmgr -sysres were:
<samples>0</samples>
<sample_buffers>0</sample_buffers>
<surface_type>EGL_PBUFFER_BIT|EGL_PIXMAP_BIT|EGL_LOCK_SURFACE_BIT_KHR</surface_type>
</config>
</configs>
</egl>
<wfd>


use -i /sbin/io-winmgr reports:
NAME=io-winmgr
DESCRIPTION=compositing window manager
DATE=2009/04/15-09:25:09-EDT
STATE=experimental
HOST=cctrunk
USER=builder
VERSION=6.4.0
TAGID=9999@218225


Is this hangup to be expected or it's something with our configuration or our use of the command?