Hi The graphical Debian installer, which is basically a GTK on DFB tool, is going to (hopefully) support three different HW architectures: i386, AMD64 and PPC. i386 and AMD64 seem to be less problematic to support, but things are worse for PPC (DFB 0.9.25 is currently used ).
First, IIUC, there are three modes DFB can operate respect to hip-specific kernel framebuffer devices and a chip-specific DFB gfxdrivers 1) chip specific fb driver + chip specific gfxdriver (e.g.: i810fb + libdirectfb_i810) 2) chip specific fb driver + generic gfxdriver (e.g.: i810fb + no-hardware) 3) generic fb driver + generic gfxdriver (e.g.: vesafb + no-hardware) Now, on i386 and AMD64 we issue video=vesa at boot time and have "no-hardware" in directfbrc, so we should be in case 3, right? This is ok for us, as we don't mind performance and are interested in maximum reliability only. On PPC, where a generic fb module is not available (is this correct?) we have following fb devices built into the kernel ( and have "no-hardware" in directfbrc, so we should be in "mode 2" ) offb, controlfb, platinumfb, valkyriefb, imsttfb, nvidiafb, matroxfb, radeonfb, aty128fb, atyfb, sisfb and 3dfxfb. and we did some test with ATI and nvidia chips on powermacs, and the results are reported in our wikipage [1]. Are such results something expected? is there any trick we may try to get things to work (boot parameters, directfb configuration options..) ? thanks Attilio [1] http://wiki.debian.org/DebianInstaller/GUIToDo _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
