Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Loading modules with device tree after rootfs is mounted
Date: Sat, 27 Feb 2016 13:09:13 +0100	[thread overview]
Message-ID: <56D191E9.3050604@mind.be> (raw)
In-Reply-To: <87wppqsbfo.fsf@dell.be.48ers.dk>

On 02/27/16 11:19, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> 
>  > On 30-01-16 18:56, Tim Michals wrote:
>  >> I've created new buildroot defconfig for Udoo Neo board, u-boot, linux kernel
>  >> boots and busybox prompt is active and accepts commands.  The issue is several
>  >> drivers (wifi, camera, etc) are built as kernel modules and stored on ext4
>  >> rootfs.  How can the kernel load these modules via the device tree from the rootfs? 
> 
>  >  The kernel doesn't automatically load modules, you need a userspace hotplug
>  > helper to handle that. You have the following options:
> 
>  > 1. modprobe the required drivers in an init script (no hotplugging).
>  > 2. Write a hotplug script that modprobes as required (google it).
>  > 3. Use mdev as the /dev handler and add a modprobe handler in mdev.conf (google it).
> 
> We should really fix our mdev setup to do this correctly out of the
> box. I don't usually use mdev, but I've just tried it on the pandaboard
> which has the same problems as the kernel config builds almost
> everything as modules.
> 
> As far as I can see from looking at the code and googling it, we need
> to:
> 
> - Add a line to mdev.conf to support dynamic module loading:
> 
> # load modules
> $MODALIAS=.*    0:0 660 @modprobe "$MODALIAS"

 that's right.

> 
> - Add a line to the init script for cold plugging modules (E.G. modules
> for which the devices were already present before mdev was added as the
> hotplug handler). mdev -s should arguable handle this, but it doesn't.

 Well, mdev was not originally meant to do the module probing, it's more of a
hack on top of it. mdev was meant for changing names and permissions of device
nodes. So in the coldplug (mdev -s) it will just handle the device nodes it
finds in /sys/class.

> 
> find /sys/ -name modalias | xargs sort -u | xargs modprobe -abq

 I wouldn't have thought of the sorting, but looks good to me.

 Regards,
 Arnout

> 
> I'll send a patch to add this, but it would be good if somebody who
> is more familiar with mdev could take a look.
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-02-27 12:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 17:56 [Buildroot] Loading modules with device tree after rootfs is mounted Tim Michals
2016-01-31 22:52 ` Arnout Vandecappelle
2016-02-27 10:19   ` Peter Korsgaard
2016-02-27 12:09     ` Arnout Vandecappelle [this message]
2016-02-27 17:57       ` Peter Korsgaard
2016-02-27 20:46         ` Arnout Vandecappelle
2016-02-27 21:47           ` Peter Korsgaard

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=56D191E9.3050604@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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