All,
Has anybody else experienced their osd0 layer just going black after 5
minutes of idling? Some background. There are times when we have to do
a system software update which loads updated software to various
devices, including other processors. When this happens, no other
applications (other than system daemons called out in /etc/inittab) are
running.
In order to keep the user appraised of what's going on with the system,
different status images are copied into /dev/fb/0 which give feedback as
to what's happening. I was running into the console going blank
leaving the user completely unaware as to what was going on, but that
was fixed by setting the blankinterval in vt.c to 0. Now I've run into
another problem where the screen goes black after 5 minutes, presumably
by fbcon but i have no clue.
I'm connect to an LCD so I can measure my digital rgb lines (vsync,
Hsync, dotclk) and they're all clocking nicely, but my RGB lines lose
their data, they simply go high. Presumably this is another 'helpful'
screen saver option that is built into the framebuffer, but i have NO
CLUE as to where this is implemented so I can either turn it off, or at
the very least increase the time.
Does anybody have any clues to this? I've searched the list, and saw
the 'setterm' posts, but that is for the terminal and I've already taken
care of that issue by setting the interval to 0 in vt.c
Thanks,
BJ
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
