Re: make module_install

Re: make module_install

[Wolfgang Denk]

In message <002301c2a5fd$918c5fc0$0700a8c0@pc005> you wrote:
>
> Many are the things that we must learn (from Linux point of view) before
> release some code under GPL, and we shouldn't like to release something that
> could be a bad example.

Do not hesitate to relase your code early. This is one of  the  basic
ideas  of  Open  Source  development,  and  a  source  of huge mutual
benefit: first, a duplication of effort may  result,  as  others  can
pick  up your results early instead of starting the same project just
because they  didn't  know  about  yours;  second,  you  may  receive
feedback  which  helps  you  to solve or avoid problems or to improve
your code.

The good old rule is: release early, release often.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In the beginning there was nothing.
And the Lord said "Let There Be Light!"
And still there was nothing, but at least now you could see it.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: make module_install

[Wolfgang Denk]

In message <20021217190611.AA903C6139@atlas.denx.de> I wrote:
...
> Do not hesitate to relase your code early. This is one of  the  basic
> ideas  of  Open  Source  development,  and  a  source  of huge mutual
> benefit: first, a duplication of effort may  result,  as  others  can
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Nonsense. I meant: duplication of effort can be AVOIDED

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
On a clear disk you can seek forever.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: make module_install

[Marius Groeger]

On Wed, 18 Dec 2002, Allen Curtis wrote:

> I think I have followed this thread to the end and I don't see a solution to
> the module problem? If that is the case, I noticed in the original message
> that ARCH=ppc was specified but the CROSS_COMPILE= was not. ARCH really only
> affects make menuconfig. (from my experience) But if you do not specify the
> correct compiler you will definitely get complaints about not having a
> compatible architecture.

I think the solution was given quite early by Jaap-Jan Boor: use the
Busybox depmod Perl script, if you need one.

Regards
Marius

-----------------------------------------------------------------------------
Marius Groeger           SYSGO Real-Time Solutions AG       mgroeger@sysgo.de
Software Engineering     Embedded and Real-Time Software    www.sysgo.de
Voice: +49-6136-9948-0   Am Pfaffenstein 14                 www.osek.de
FAX:   +49-6136-9948-10  55270 Klein-Winternheim, Germany   www.elinos.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: make module_install

[Wolfgang Denk]

In message <001301c2a5ed$1d546ea0$0700a8c0@pc005> you wrote:
>
> > make modules_install INSTALL_MOD_PATH=/opt/eldk/ppc_8xx
>
> By doing that I have solved only the 50% of the problem. In fact now the
> files are moved in the right place but the message still exist.

I know. I tend to simply ignore it ;-)

> It seems that the architecture of the ELF files was wrong or the depmod runs
> for an i386 architecture.

The latter is the case: you are running a host-depmod  but  a  cross-
depmod  is  needed.  Feel  free to change the defintiion of DEPMOD in
your top-level makefile to your liking.

IMHO this is overkill, though. For  standard  desktop/server  systems
modules are used to be able to run the same kernel version for a wide
range  of  hardware  configurations;  but the situation is completely
different for embedded systems: modules are  usually  only  used  for
driver  development,  and  then you will manually load and unload the
driver anyway. I will even go so far to say that if you need  to  run
"depmod"  for  your embedded system you should fix your system design
because you are doing something wrong.

Of course, YMMV.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In theory, there is no difference between  theory  and  practice.  In
practice, however, there is.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: make module_install

[Marius Groeger]

On Tue, 17 Dec 2002, Wolfgang Denk wrote:

> different for embedded systems: modules are  usually  only  used  for
> driver  development,  and  then you will manually load and unload the
> driver anyway. I will even go so far to say that if you need  to  run
> "depmod"  for  your embedded system you should fix your system design
> because you are doing something wrong.

Someone might use loadable modules because he doesn't want to release
his driver under the GPL. I wouldn't exactly consider this wrong.

Regards,
Marius

-----------------------------------------------------------------------------
Marius Groeger           SYSGO Real-Time Solutions AG       mgroeger@sysgo.de
Software Engineering     Embedded and Real-Time Software    www.sysgo.de
Voice: +49-6136-9948-0   Am Pfaffenstein 14                 www.osek.de
FAX:   +49-6136-9948-10  55270 Klein-Winternheim, Germany   www.elinos.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: make module_install

[Wolfgang Denk]

In message <Pine.LNX.4.40.0212171909030.11803-100000@mag.devdep.sysgo.de> you wrote:
>
> > driver anyway. I will even go so far to say that if you need  to  run
> > "depmod"  for  your embedded system you should fix your system design
> > because you are doing something wrong.
>
> Someone might use loadable modules because he doesn't want to release
> his driver under the GPL. I wouldn't exactly consider this wrong.

I do not intend to comment on the issue of binary modules.

But even in such a situation  the  necessity  to  run  depmod  in  an
embedded  system is IMHO an indication of a potential design problem.
Things should be kept simple.


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
No user-servicable parts inside. Refer to qualified service personnel.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: make module_install

[Wolfgang Denk]

Dear Gianfranco,

in message <000701c2a5e5$30b5a660$0700a8c0@pc005> you wrote:
>
> I have implemented a loadable driver and I have compiled the source code
> with the command "make modules". When I try to run the install script with

OK so far.

> the command "make modules_install" it exits with the following message:

This is wrong; it will try to install the modules not on your  target
filesystem,  but  on your development host, and (if you're running as
root and the copy actually succeeds - which is another mistake: never
do such things  as  root!)  your  development  host's  "depmod"  will
complain.

You should pass a "INSTALL_MOD_PATH=<target_dir>" parameter  to  your
make command, something like

	make modules_install INSTALL_MOD_PATH=/opt/eldk/ppc_8xx

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There are three ways to get something  done:  do  it  yourself,  hire
someone, or forbid your kids to do it.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/