From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] BuildRoot not starting with Udev
Date: Wed, 17 Oct 2012 13:07:45 +0200 [thread overview]
Message-ID: <507E9181.5060000@mind.be> (raw)
In-Reply-To: <CA+mmYj1=cP3p24SnQ3HsRxQUo_gJBQidGXv5EiVKZc2D7kfjZQ@mail.gmail.com>
On 17/10/12 13:03, 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?
The DEVTMPFS is set automatically by buildroot - but only when configuring
the kernel. Once your kernel is configured, it's not touched again.
So you'd have to run 'make linux-reconfigure' to get the devtmpfs (note that
you also loose your local modifications that way, unless you saved them to
a custom defconfig).
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-10-17 11:07 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 [this message]
2012-10-17 11:15 ` Antoine Caurier
[not found] ` <CA+mmYj34+xbUcq=jvEuTFRu_XwX3TMn1Bcv6Rwnnn17pDCewiA@mail.gmail.com>
2012-10-17 17:23 ` Thomas Petazzoni
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=507E9181.5060000@mind.be \
--to=arnout@mind.be \
--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