I have encountered the same problem. I didn't want to delete
buildroot_arm_nofpu because I just built a new kernel in there and
that's what I wanted to test. But the new kernel did not contain cfio.ko
and mcf.ko anymore. I checked that "wifistix" was checked before making
the buildroot, after making the kernel, but the marvel modules were
still not the final image. It looks like buildroot thinks the modules
are in place, so doesn't overwrite them from the marvel-binaries, but by
building the kernel they were removed.
This is a very good example why things keep going wrong if your "design"
is wrong in the first place! If the drivers source code were open, the
whole system would compile like a breeze. :-)
Oh, BTW if you just extract/copy the modules from
gumstix-buildroot-nocfio/dl/marvell-binaries-2.6.18-1.tar to your
gumstix after you transfer the new image to it, it should work just
fine. Just make sure your kernel is the same version as the binary modules.
Dave Hylands wrote:
> Hi Mark,
>> However, after I go into the linux-2.6.18gum dir., add new features
>> (via menuconfig) and then rebuild; the marvell drivers are no longer
>> present in the kernel modules/drivers dir under /root. And life is bad.
> Hmmm. There is no reason for them to disappear. I'll give it a whirl
> tonight when I get home.
> When you do the menuconfig command inside the linux-2.6.18gum dir are you doing:
> make ARCH=arm menuconfig
> Oh wait a minute - are you doing the make from within the linux
> directory? I normally do the following from the gumstix-buildroot
> rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux
> Doing the rm will cause the top-level make to run make on the kernel
> with all of the appropriate command line options.
>> Can I simply untar the marvell-binaries file that's in the download
>> dir. to put these drivers back in right locations, or is there more to
>> it than that??
> The modules.dep and modules.symbols probably need to be updated as
> well. depmod normally does this automatically, but if the modules are
> missing it won't.