On Mon, Nov 28, 2005 at 05:10:36PM +0100, Attilio Fiandrotti wrote: > Denis Oliver Kropp wrote: > >Quoting Mike Emmel: > > > >>Finally and sorry for three posts If I'm right about this then the fix > >>is to not install signal handlers but use either semaphors which are > >>safe or easier sigwait similar to the following code > >> > >>http://www.awprofessional.com/content/images/0201633922/sourcecode/sigwait.c > > > > > >For the VT switching stuff, this looks like a good idea. > > > >But I'm not sure if we should change it for all other signals, maybe some. > > > > According to mike's suggestions i've tried to write the patch to this > bug but i've not been able to test it since it's a week that i cannot > run simple DFB apps on both the PCs i own. > The standard "simple" tutorial app from DFBTutorials-0.5.0 no longer > works and i always get this error message > > (!!!) *** WARNING [fbdev driver possibly buggy] *** [fbdev.c:1736 in > dfb_fbdev_set_mode()] > (!!!) *** ONCE [unsupported destination format] *** [generic.c:6314 > in gAcquire()] > > This happens with DFB 0.9.22, 0.9.24 and 0.9.25 from CVS. > On my laptop is installed a 2.6.14 kernel and on my desktop pc is > installed 2.6.12 from un unstable Debian distro. > Both kernels support framebuffer and are passed "video=vesa:ywrap,mtrr > vga=788" at boot time.
The correct format with 2.6 kernels is video=vesafb:... -- Ville Syrjälä [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
