All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: linux cbon <linuxcbon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: how to have the kernel do udev's job and autoload the right modules ?
Date: Tue, 05 May 2015 01:24:40 +0200	[thread overview]
Message-ID: <5547FFB8.5050007@nod.at> (raw)
In-Reply-To: <CAJ-LWjMMKF1hbGUxxLPXPvq++hpCyFb7+VtMu8jLO66j=mv6cw@mail.gmail.com>

Am 05.05.2015 um 01:14 schrieb linux cbon:
> On Mon, May 4, 2015 at 7:21 PM, Richard Weinberger <richard@nod.at> wrote:
>> You can build in the needed modules or just use udev...
> 
> for example, I need these modules to be loaded automatically by the kernel,
> but they are not : r8169 , radeon , snd_hda_codec etc.
> Why doesn't the kernel do it, instead of using a userspace program like udev ?
> Sorry if my question is silly.

Because in some cases you want to blacklist modules, have special parameters for
them etc...
It is a typical "kernel offers mechanism and userspace policy" thing.

If you want them blindly loaded add them to your local.rc or build them in.

Thanks,
//richard


  reply	other threads:[~2015-05-04 23:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04  5:31 how to have the kernel do udev's job and autoload the right modules ? linux cbon
2015-05-04  7:34 ` Richard Weinberger
2015-05-04 17:27   ` linux cbon
2015-05-04 18:21     ` Richard Weinberger
2015-05-04 18:30       ` Austin S Hemmelgarn
2015-05-04 23:14       ` linux cbon
2015-05-04 23:24         ` Richard Weinberger [this message]
2015-05-05 18:08           ` linux cbon
2015-05-05 22:26             ` Ken Moffat
2015-05-06  0:54               ` linuxcbon linuxcbon
2015-05-06 16:55                 ` Ken Moffat
2015-05-06 17:09                   ` linuxcbon linuxcbon
2015-05-06 18:40                     ` Ken Moffat
2015-05-06 18:53                     ` David Lang
2015-05-06 20:34                       ` linuxcbon linuxcbon
2015-05-06 20:36                         ` Richard Weinberger
2015-05-06 20:49                         ` David Lang
2015-05-07 12:04                           ` Austin S Hemmelgarn
2015-05-07 19:19                             ` David Lang

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=5547FFB8.5050007@nod.at \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxcbon@gmail.com \
    /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.