From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sun, 28 Jul 2013 15:51:56 +0200 Subject: [Buildroot] [PATCH] busybox: register mdev as hotplug helper In-Reply-To: <51F51EBE.4000701@zacarias.com.ar> References: <1373574654-32427-1-git-send-email-gustavo@zacarias.com.ar> <51DFDA1F.60904@zacarias.com.ar> <51F50077.2060204@zacarias.com.ar> <20130728151418.70891325@skate> <51F51EBE.4000701@zacarias.com.ar> Message-ID: <20130728155156.1bc37ffd@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Gustavo Zacarias, On Sun, 28 Jul 2013 10:38:06 -0300, Gustavo Zacarias wrote: > >> Proven failure: not building a kernel with buildroot. > > > > Not really an argument: if you select 'devtmpfs' as the /dev management > > method and you build your kernel outside of Buildroot, you have to > > enable CONFIG_DEVTMPFS + CONFIG_DEVTMPFS_MOUNT, otherwise things won't > > work. I don't see what it shouldn't be the same for the hotplug helper > > selection: if you're building the kernel with Buildroot, then things are > > taken care of automatically, otherwise you're on your own. > > Then we should just ditch the device managment options if the user isn't > building a kernel? No because it also controls whether the device_table_dev.txt is use to create static devices or not. It also controls whether the udev package is built, etc. So clearly the device management options aren't just controlling the kernel configuration, but a lot of other things as well. > For mdev that can be solved, at worst it'll be an (almost) no-op, > devtmpfs is another story. That's true. Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com