From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: module dependency files
Date: Wed, 22 Oct 2003 08:57:33 +0200 [thread overview]
Message-ID: <20031022065732.GP20846@lug-owl.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0310211814340.14473-100000@ares.mmc.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Tue, 2003-10-21 18:15:56 -0400, David Kesselring <dkesselr@mmc.atmel.com>
wrote in message <Pine.GSO.4.44.0310211814340.14473-100000@ares.mmc.atmel.com>:
> That's what I did. I defined INSTALL_MOD_PATH as $(TOPDIR)/modules. The
> modules get put there but depmod fails.
depmod works on it's own architecture and I don't recall a way that
would make it work on cross-compiled modules. Maybe you should just copy
over the modules (INSTALL_MOD_PATH is a good start here) and execute
depmod on the target system...
Apart from that, insmod (instead of modprobe) should always work,
though...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-22 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 21:22 module dependency files David Kesselring
2003-10-21 21:25 ` Jeff Angielski
2003-10-21 21:25 ` Jeff Angielski
2003-10-21 22:15 ` David Kesselring
2003-10-22 6:57 ` Jan-Benedict Glaw [this message]
2003-10-22 8:02 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 7:14 Colin.Helliwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031022065732.GP20846@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox