From: "Dave Hylands" <dhylands@gmail.com>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: linux-embedded@vger.kernel.org
Subject: Re: modules.dep and depmod.pl
Date: Fri, 13 Jun 2008 23:51:38 -0700 [thread overview]
Message-ID: <c32efac40806132351t150259e3oc0214e3ccd5eb6c@mail.gmail.com> (raw)
In-Reply-To: <63386a3d0806131633g4721216al566c8b6959e4631@mail.gmail.com>
Hi Linus,
> I tried this thing to be able to modprobe off a read-only flash
> rootfilesystem and it "sort of" works, actually.
>
> However there is no way you will pass this to the kernel DEPMOD
> parameter, I only ever get this to work when doing it after
> compilation, as a separate step.
I think it depends on which version of busybox you use.
When we were using 1.01 I think I had to patch the kernel Makefile. I
think I had to undo my patch when we upgraded to the 1.10 version of
busybox.
I'll have to wait until I get back to work on Monday to check.
> Is there anyone beside me who would like to see this integrated
> into scripts/ in the kernel to get some default modules.dep for
> a read-only rootfs also when doing cross compilation, or am I
> totally going down the wrong lane here?
You can also run the busybox depmod.pl after you've built the kernel,
but before you make the file system.
--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/
next prev parent reply other threads:[~2008-06-14 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63386a3d0806131611g61ad6ab1t16bc68ab6407a8dc@mail.gmail.com>
2008-06-13 23:33 ` modules.dep and depmod.pl Linus Walleij
2008-06-13 23:45 ` Mike Frysinger
2008-06-14 17:00 ` Bernhard Fischer
2008-06-14 6:51 ` Dave Hylands [this message]
2008-06-14 19:23 ` Linus Walleij
2008-06-14 9:26 ` Matthieu castet
2008-06-14 19:38 ` Linus Walleij
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=c32efac40806132351t150259e3oc0214e3ccd5eb6c@mail.gmail.com \
--to=dhylands@gmail.com \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-embedded@vger.kernel.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).