[ELDK] Selecting and compiling modules

[Pitch Klein]

Thanks,

It seems that I can't use menuconfig, because I don't have ncurses libraries
installed. Before I try to install them on my own, is there any difference
with "config"?? because it seems I can run that, althoguh there are many
many options and I often don't know what to choose. I'm guessing pressing
[Enter] leaves each variable as it was and lead to the next one. Is that
right?



On Thu, Dec 2, 2010 at 7:40 PM, Anatolij Gustschin <agust at denx.de> wrote:

> Hello,
>
> On Thu, 2 Dec 2010 19:06:38 +0100
> Pitch Klein <pitchklein at gmail.com> wrote:
> ...
> > I've been able to compile and download an image of the last kernel that
> you
> > provide, and boot it from the board, with the root filesystem located in
> my
> > host PC.
> >
> > I want to try a specific driver that I thought was included in the
> kernel,
> > but when I try to prove the corresponding module... it just isn't there.
> So
> > I checked /lib/modules in my corresponding eldk installation folder to
> see
> > if it was there. I see it is not. there ar two folders, that finally
> contain
> > only some iscsi related .ko files. So I guessed I had to use the cross
> > compiler in the eldk to compile my module, add it to that folder, and try
> > modprobe from the board.
>
> Yes. Also don't forget to run "depmod -a" before loading with
> modprobe.
>
> > It happens that typing "make ARCH=powerpc CROSS_COMPILE=4xxFP- " on the
> > module source folder wouldn'r work. There is a makefile there, but
> whenever
> > I try I get the message: "no rule to build object XXXXX"
>
> You are supposed to run "make ARCH=powerpc CROSS_COMPILE=ppc_4xxFP-
> modules"
> in the top level directory of the Linux kernel source, but not in
> the module source directory.
>
> > I then checked again the DULG documentation and saw that there's a line
> that
> > reads:
> > "...In case you configured modules you will also need to compile the
> modules
> > make ARCH=powerpc CROSS_COMPILE=4xxFP- modules
> > and install the modules..."
> >
> > I do that, but it seems only some modules are compiled, not all, and
> > definitely not the one that I need.
>
> Probably the module you need is not selected in your kernel
> configuration. Try running
> "make ARCH=powerpc CROSS_COMPILE=ppc_4xxFP- menuconfig"
> and look if the module is selected or not. If not, select it, save
> the new configuration and then run make again:
>
> make ARCH=powerpc CROSS_COMPILE=ppc_4xxFP- modules
> make ARCH=powerpc CROSS_COMPILE=ppc_4xxFP-
> INSTALL_MOD_PATH=/opt/eldk/ppc_4xxFP/ modules_install
>
> The module installation directory in the command above is
> only an example, you need to specify your module directory according
> to your ELDK setup.
>
> > I wonder then what "configured modules" mean.,. so* here's my question*:
> >
> > *Is there a way so I can select a module from the kernel to be compiled
> with
> > the cross compile tool????? If so, how??*
>
> Please see the description above.
>
> Best regards,
> Anatolij
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
>