Hello,
On 06/09/04 19:29, Nicolas Huillard wrote:
I would like to have clear requirements for the system to work :
My main developing and testing machine is a EPIA M10000.
* can I / must I compile viafb as a module, or in-kernel
As a module.
* can I / shoudn't I also compile vesafb (in-kernel, as a module) ?
No, don't do that. vesafb will grab you gfx adapter.
I did compile vesafb as a module, but didn't load it. This was just to
have to opportunity to load cle266vgaio on top of vesafb (
* is there any other module that I should compile, are the versions
important ? (agpgart, via_v4l_drv, drm, fusion, fbgen (?), etc.)
If you plan to compile DirectFB with multiapplication core, you'll need
fusion:
http://directfb.org/cgi-bin/cvsweb.cgi/linux-fusion/
* what order should these modules be loaded, if compiled as modules ?
* what version of DirectFB should I use ? (I tried 0.9.20 from Debian
testing, and a self compiled 0.9.21-cvs, checked out last sunday)
Bleeding edge CVS. ;-)
> * what other DirectFB libraries should I use ? (FusionSound, etc.)
FusionSound is mandatory, so is libavcodec. I'm still using 0.4.8
* my /etc/fb.modes file came from Debian, and does not seem to be suited
to the CLE266 : is there a source for a good fb.modes file ?
I'm using:
mode "720x576-50Hz-16bit"
geometry 720 576 720 576 32
timings 31208 144 40 32 10 128 3
bcast true
endmode
* what screen resolution works best with VDR/softmpeg, and how can I
check working screen resolutions (when I have vga=ask in lilo.conf, and
viafb compiled-in, a scan of available modes freezes the kernel).
My startup looks like this:
# DirectFB multiapplication core
modprobe fusion
# viafb + set right mode
modprobe viafb refresh=50 mode=720x576 TVon=1 TVoverscan=1 bpp=32