Framebuffer driver now (DVSDK 1.30) implements the fb_blank method to disable/enable windows, you may see a window get blanked unexpectedly if your kernel includes the framebuffer console driver or if you are running a GUI (like X Windows) on top of a framebuffer. The fb_blank method is commonly used to implement a 'screen saver' function.The default behavior of the kernel framebuffer console driver is to blank the screen after 10 minutes of inactivity. Inactivity is defined as no input from the keyboard or mouse. The astute observer will notice that the DaVinci normally has neither a keyboard nor a mouse connected to it, so 10 minutes of inactivity is typically equivalent to 10 minutes after you boot the kernel. At this point the kernel framebuffer console driver will blank virtual console 0, which corresponds to OSD0 on the DaVinci. If you booted with the default window configuration, you will be left staring at whatever image happens to be in the VID1 framebuffer and wondering where your OSD0 window went.There are a couple of things you can do to avoid unexpected screen blanking.
First, you can disable framebuffer console support in the kernel by building a kernel with the CONFIG_FRAMEBUFFER_CONSOLE option disabled. It is highly unlikely you would ever actually want to use a framebuffer console with a DaVinci anyway.
If you don't want to disable the framebuffer console, you can disable blanking via the setterm application as follows: setterm -blank 0 > /dev/vc/0
