linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: alebas@televes.com
To: linuxppc-embedded@ozlabs.org
Subject: depmod.pl script & kernel 2.6
Date: Mon, 13 Dec 2004 14:32:59 +0100	[thread overview]
Message-ID: <1102944779.41bd9a0b9155f@webmail.televes.com:443> (raw)

Hi all,

Till now I've been using the ELDK 3.0 framework for development.
Now I am involved in some development on kernel 2.6, and I would
prefer using kernel modules. But I can't get script depmod.pl in
eldk/usr/sbin working with kernel 2.6 modules.

I've checked for a new version of this script on Busybox (I think
it's the same than ELDK's one), but since version 1.0 this is not
available.

So, how are you coping with this? Is there any way to use ELDK
with kernel 2.6 modules? Or should I change to another framework?

Currently, I work with ELDK on an i686 system, cross-compiling
onto PPC with the ppc_82xx- toolchain included in the ELDK.
I use the SELF's RamFS from the ELDK, with Busybox shell and
modutils. The depmod.pl script creates the modules.dep file
in this rootfs.

Thanks,

Alex

                 reply	other threads:[~2004-12-13 13:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='1102944779.41bd9a0b9155f@webmail.televes.com:443' \
    --to=alebas@televes.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).