Quoting Jiri Svoboda ([EMAIL PROTECTED]): > Hi, > > Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > > > Hi, > > > why is first framebuffer (or X) blanked while using second? I shoul use > > > some switch to prevent this? Or vt from which the process is started is > > > always blanked? > > > > I guess the blanking is caused by the switch to a new vt that is > > allocated by DirectFB. You may try the "--no-vt-switch" option, > > but another problem will be the usage of input devices. I don't > > Yes, it's true. Question to the developeres: could DirectFB open the new vt > on _propriate_ framebuffer?
There's an ioctl FBIOPUT_CON2FBMAP that sounds like doing the right thing. I just tested 'con2fbmap' and both screens displayed a VT, but only one VT was active. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" convergence integrated media GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
