From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BuildRoot not starting with Udev
Date: Wed, 17 Oct 2012 19:23:37 +0200 [thread overview]
Message-ID: <20121017192337.7f1ac3eb@skate> (raw)
In-Reply-To: <CA+mmYj34+xbUcq=jvEuTFRu_XwX3TMn1Bcv6Rwnnn17pDCewiA@mail.gmail.com>
Hello Antoine,
On Wed, 17 Oct 2012 10:22:22 +0200, Antoine Caurier wrote:
> I found one of your previous post, where you said that if kernel was
> build by buildroot, it should be ok. So I was thinking that it should
> be ok just activating udev as I am building kernel with buildroot.
>
> I tried to manually set DEVTMPFS in linux-menuconfig, and then
> recompile the kernel (with buildroot), and it is now working.
>
> Is it normal to have manualy to set DEVTMPFS in kernel configuration
> in order to have udev working?
No, but it depends on what you did exactly.
If you did:
1) Configure /dev management as static
2) Configure your kernel
3) Build Buildroot
4) Reconfigure /dev management as udev
5) Build Buildroot
Then yes, it is normal: Buildroot doesn't try to be smart about
this kind of dependency. If you change the /dev management style, you
are responsible to restart the build of the kernel (make
linux-dirclean; make) so that it gets a configuration that is
compatible with a dynamic /dev management.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-17 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:55 [Buildroot] BuildRoot not starting with Udev Antoine Caurier
2012-10-16 17:41 ` Thomas Petazzoni
2012-10-17 11:03 ` Antoine Caurier
2012-10-17 11:07 ` Arnout Vandecappelle
2012-10-17 11:15 ` Antoine Caurier
[not found] ` <CA+mmYj34+xbUcq=jvEuTFRu_XwX3TMn1Bcv6Rwnnn17pDCewiA@mail.gmail.com>
2012-10-17 17:23 ` Thomas Petazzoni [this message]
2012-10-18 7:38 ` Antoine Caurier
2012-10-16 18:43 ` Arnout Vandecappelle
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=20121017192337.7f1ac3eb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox