imx53 mfw_isink vssconfig configuration

[janiscoders]

Hi, we are developing our custom board based on imx53 QSB using Yocto building system. Recently tried to use mfw_isink element, which allows to display multiple videos

on the same display at the same time. I am no specialist in Linux graphic system (framebuffer, x11), so it would be great if someone explained me these issues:

1) When I boot board with lvds screen without any configurations, I have everything as expected - the linux boot information with login prompt can bee seen on display.

If I play video or live camera using mfw_v4lsink, everything plaus fine fullscreen and goes back to previous display.

BUT playing videos with mfw_isink doesn't work out of the box. I read somewhere that /usr/share/vssconfig has to be changed and set fb to 0.

What really is this vssconfig file? Is there a documentation available? What does this command (fb) do and why it is set to 1 by default?

2) The multimedia documentation says that I have to set this env variable (export VSALPHA=1). I don't really understand the purpose of it and is it really needed?

3) If I play anything with mfw_isink then at first time video is playing, but everything is blinking in many colours. After that the display doesn't go back to previous

state like it does for mfw_v4lsink (i.e. the login screen isn't displayed anymore). It isn't refreshed in reality, because I can see the little blinking underscore only.

Playing video again it plays without colour blinking.

4) After a while video playing using mfw_v4lsink doesn't work anymore (it works, but nothing is being displayed. Probably something has timed out or somthing).

Anyway mfw_isink still shows video at this state.

It would be great if someone answered at least to some of these questions. Thatnk you :smileyhappy: (it would be great, getting isink to work, because it is really powerful)

[janiscoders · Accepted solution]

I think I found answers to my questions by myself.

1) Seems like /usr/share/vssconfig file is used by mfw_isink plugin and is cached (if you change something, then /dev/shm/ must be cleared [or reboot] to enable new configurations ).

Yocto dora branch at this time doesn't change vssconfig fb_num value, which by default is 1 - and that does nothing for master screen.

Seems like mfw_isink on exit sets framebuffer to sleep, that’s why screen doesn't go to previous state, like it is with mfw_v4lsink (this is only relevant when fb_num is set to 0) Read further....

In reality the fb_num must be set to value 2, then mfw_isink doesn't set framebuffer to sleep and everything goes back to normal.

2) If fb_num is set to correct value: 2, then this environment exporting is needed to see mfw_isink output. I did the export in /etc/profiles, so it would be global.

3) Previously I changed fb_num value to 0, which I think overlapped with terminal fb and thats why there was flickering conflict. If fb_num is set to 2, then there is no flickering.

4) Linux framebuffer goes to sleep after 10 minutes (this is the default), that’s why screen disappears. To disable/change this you must pass kernel parameter or write commands to /dev/tty1.

More info here:

www.armadeus.com/wiki/index.php?title=FrameBuffer

Change Linux console screen blanking behavior - Super User

[LeonardoSandova]

rogeriopimentel, could you please check the above points and make any comments if necessary.

Janis, it looks to me that you may have to create a patch to change the vssconfig value. Can you share these results in the same thread you started on the meta-freescale list?

[LeonardoSandova]

Could you send this to the meta-freescale list? There were some issues on iMX6 regarding isink, but not related to the ones above. Please post logs on each issue you faced.

Leo

[janiscoders]

I fixed some of my first problems (not the ones described here) using meta-freescale and read the old mail archive, where people had  problems with isink and they were a little related, but didn't answer everything.
What I am really interested in - is this vssconfig file. What are the configuration possibilities and how they are related? Not really sure if this is Yocto related, thats why I am asking here.

Only maybe the 4th question could be asked in meta-freescale.