From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] busybox: register mdev as hotplug helper when selected
Date: Sun, 28 Jul 2013 19:19:19 +0100 [thread overview]
Message-ID: <51F560A7.8020609@carallon.com> (raw)
In-Reply-To: <20130728143214.749C19AD30@busybox.osuosl.org>
On 28/07/2013 15:32, Thomas Petazzoni wrote:
> commit: http://git.buildroot.net/buildroot/commit/?id=caae7fa1d737c550b4a2f557d6e1761b93934340
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> It's also done in the kernel configuration, however users may be using
> some other pre-built kernel and miss functionality like firmware
> loading.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> package/busybox/S10mdev | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/package/busybox/S10mdev b/package/busybox/S10mdev
> index c06aa20..d386d42 100644
> --- a/package/busybox/S10mdev
> +++ b/package/busybox/S10mdev
> @@ -6,6 +6,7 @@
> case "$1" in
> start)
> echo "Starting mdev..."
> + echo /sbin/mdev >/proc/sys/kernel/hotplug
> /sbin/mdev -s
> ;;
> stop)
If you make that change surely you should change linux.mk to no longer
set the option? Very confusing to have both at the same time.
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
prev parent reply other threads:[~2013-07-28 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-28 14:32 [Buildroot] [git commit] busybox: register mdev as hotplug helper when selected Thomas Petazzoni
2013-07-28 18:19 ` Will Wagner [this message]
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=51F560A7.8020609@carallon.com \
--to=will_wagner@carallon.com \
--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 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.