You have part of the driver compiled into the kernel, and part as a
module. I would recommend making everything be compiled in. So all
those things that are "=m" need to be "=y". Let's see if that helps.
Julien Lebot wrote:
This depends on whether you compiled the driver as a module or if it was
compiled into the kernel. If you compiled it into the kernel, it should
just be there - nothing more to do. If however it is a module, then you
need to insert it with the "modprobe" command. Pay particular attention
to the .config line "CONFIG_FB=y". This means that the driver is part
of the kernel. If it said "CONFIG_FB=m" then the driver is a module.
If you like, cut and paste the relevant parts of your .config so we can
take a look at it. If you are getting an error message, then we need to
figure out why, because it is unlikely to work until that is resolved.
Yep, I think (well I hope) that I have badly configured the kernel ;)
# Graphics support
# CONFIG_FIRMWARE_EDID is not set
# CONFIG_FB_DDC is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_MBX is not set
# CONFIG_FB_VIRTUAL is not set
You can specify any or all of the settings in the bootargs. Whatever
you don't specify will take the default, so as long as that is what you
want then that is ok.
Ok so 128x128-16 is enough, I think I've seen that in the source code, only
the necessary options are overriden.
MSN Messenger : discutez en direct avec vos amis !
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
gumstix-users mailing list