From: Ken Moffat <zarniwhoop@ntlworld.com>
To: linuxcbon linuxcbon <linuxcbon@gmail.com>
Cc: Richard Weinberger <richard@nod.at>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: how to have the kernel do udev's job and autoload the right modules ?
Date: Wed, 6 May 2015 19:40:58 +0100 [thread overview]
Message-ID: <20150506184058.GA25814@milliways> (raw)
In-Reply-To: <CAJ-LWjOkZLGRQVVBVUnd1BWTwD+NTsfRfJoajzLyMRCmg060Jg@mail.gmail.com>
On Wed, May 06, 2015 at 06:09:39PM +0100, linuxcbon linuxcbon wrote:
> On Wed, May 6, 2015 at 5:55 PM, Ken Moffat <zarniwhoop@ntlworld.com> wrote:
> > I suggest that you take the time to look at eudev and mdev, and
> > think about how you can use the facilities they offer.
> I was wishing the kernel would offer some minimal support for
> network, sound and full screen video for my hw :(.
> But it seems I need to load modules to achieve this. And to load modules,
> it needs some kind of "hotplug" called udev or mdev.
>
Because it is something that _can_ be done in userspace, so it is
done there.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
next prev parent reply other threads:[~2015-05-06 18:41 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
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 [this message]
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=20150506184058.GA25814@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxcbon@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.