All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] mdev problem in 2011.08 ?
Date: Sun, 18 Sep 2011 16:28:42 +0200	[thread overview]
Message-ID: <20110918162842.02150727@skate> (raw)
In-Reply-To: <4E75EBBF.9080203@openwide.fr>

Hello Pierre,

Le Sun, 18 Sep 2011 15:01:51 +0200,
Pierre Ficheux <pierre.ficheux@openwide.fr> a ?crit :

> May be I'm wrong but it seems there is a problem when using mdev for
> /dev management:

For our mdev and udev support, we assume that the kernel is compiled
with CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT. For kernels built by
Buildroot, this is ensured by :

        $(if $(BR2_ROOTFS_DEVICE_CREATION_STATIC),,
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS,$(@D)/.config)
                $(call KCONFIG_ENABLE_OPT,CONFIG_DEVTMPFS_MOUNT,$(@D)/.config))

in linux/linux.mk.

For kernels built outside of Buildroot, it's up to the user to enable
those options. In your case, I guess your kernel lacks devtmpfs support
and/or the option to have devtmpfs mounted automatically at boot time,
and this explains why the /dev/null device is missing.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-09-18 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 13:01 [Buildroot] mdev problem in 2011.08 ? Pierre Ficheux
2011-09-18 14:28 ` Thomas Petazzoni [this message]
2011-09-18 16:44   ` Pierre Ficheux
2011-09-18 17:14     ` Thomas Petazzoni

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=20110918162842.02150727@skate \
    --to=thomas.petazzoni@free-electrons.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.