All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: How do I control what kernel modules are being loaded?
Date: Fri, 8 Mar 2013 19:12:13 +0100	[thread overview]
Message-ID: <20130308191213.102258ca@e6520eb> (raw)
In-Reply-To: <CAFyqS9qFQ+kHrjmDAw4mCKop6RMzH7Ws1V6tt0_A2gM2a5UmYg@mail.gmail.com>

Hi Hans,

Le Fri, 8 Mar 2013 13:08:21 +0100,
Hans Beckérus <hans.beckerus@gmail.com> a écrit :

> Hi. I have built some custom kernel modules (.ko) using a .bb that
> inherits from the module.bbclass. There is one main kernel module and
> the rest are dependent on the first. Building and installing the
> modules to the rootfs works fine. Next question is how do I control
> what actual modules are loaded at boot, or actually how do I control
> this through Yocto? To my surprise one of the kernel module loaded
> automatically!? How could this happen? I did not have an entry for it
> in /etc/modules. And what do I need to do to actually add entries to
> /etc/modules? Or is there some other mechanism that I should use. I
> tried going through the module.bbclass but must admit I lost it
> somewhere in the middle ;) Any guidance would be appreciated.
> 
when the module is built by the kernel recipe you can use :
module_autoload and you can see somme usage examples here :
http://cgit.openembedded.org/meta-handheld/tree/conf/machine/palmtx.conf
http://cgit.openembedded.org/meta-handheld/tree/conf/machine/include/palm.inc

maybe you could get inspiration from kernel.bbclass to do the same
thing in your recipe.

Eric


  parent reply	other threads:[~2013-03-08 18:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 12:08 How do I control what kernel modules are being loaded? Hans Beckérus
2013-03-08 17:12 ` Bruce Ashfield
2013-03-08 17:40   ` Hans Beckérus
2013-03-08 17:45     ` Bruce Ashfield
2013-03-08 18:12 ` Eric Bénard [this message]
2013-03-08 19:00   ` Hans Beckerus
2013-03-08 23:45     ` Bruce Ashfield
     [not found]       ` <CAFyqS9rT=amDBNTO_awzXL3zNS-vCx1+0ERCspXTps8u_VpHwA@mail.gmail.com>
2013-03-11 13:28         ` Hans Beckérus
2013-03-11 13:37           ` Bruce Ashfield
2013-03-11 13:46             ` Eric Bénard
2013-03-11 13:49               ` Bruce Ashfield
2013-03-11 13:49             ` Eric Bénard
2013-03-11 18:36               ` Hans Beckerus
2013-03-08 21:11   ` Hans Beckerus
2013-03-08 19:16 ` Trevor Woerner

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=20130308191213.102258ca@e6520eb \
    --to=eric@eukrea.com \
    --cc=hans.beckerus@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.