From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Richard Weinberger <richard@nod.at>,
linux cbon <linuxcbon@gmail.com>,
Richard Weinberger <richard.weinberger@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: Mon, 04 May 2015 14:30:40 -0400 [thread overview]
Message-ID: <5547BAD0.9070900@gmail.com> (raw)
In-Reply-To: <5547B89B.5070502@nod.at>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On 2015-05-04 14:21, Richard Weinberger wrote:
> Am 04.05.2015 um 19:27 schrieb linux cbon:
>> use request_module() and reinvent a userspace mini udev ? Well thats
>> above my skills,
>> and I though the kernel was more magical. Do you know why not give a
>> "minimal" network,
>> sound, and amd video support in the kernel, so that loading those
>> modules would be optional ?
>
> You can build in the needed modules or just use udev...
>
You might consider looking into eudev, it's a Gentoo hosted fork of udev
targeted at embedded systems, and therefore very lightweight (and it
doesn't depend on systemd).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-05-04 18:30 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 [this message]
2015-05-04 23:14 ` linux cbon
2015-05-04 23:24 ` Richard Weinberger
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=5547BAD0.9070900@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxcbon@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=richard@nod.at \
/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.