From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux: Don't enable DEVTMPFS support for kernels older than 3.x.
Date: Thu, 24 Apr 2014 08:49:14 +0200 [thread overview]
Message-ID: <87bnvr2ped.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <OF4212D2FC.25E3AE63-ON86257CC3.004F7CF7-86257CC3.007CFC5D@rockwellcollins.com> (rjbarnet@rockwellcollins.com's message of "Wed, 23 Apr 2014 17:45:18 -0500")
>>>>> "rjbarnet" == rjbarnet <rjbarnet@rockwellcollins.com> writes:
Hi,
> We recently ran into a issue where brought a board forward to use Buildroot
> 2014.02 that we kept at a kernel version of 2.6.33. Yes, I agree that we should
> be using a new kernel but the work to port to a newer version is too great but
> we needed to upgrade some package versions. The system was unable to boot
> because DEVTMPFS_MOUNT was enabled in kernel config. We traced the issue back
> to Buildroot automatically enabling these options in our kernel config. There
> was no way to not include this kernel config option when
> BR2_ROOTFS_DEVICE_CREATION_STATIC is enabled.
Huh, but we ONLY enable it if BR2_ROOTFS_DEVICE_CREATION_STATIC isn't
enabled - So why not just enabled it?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-04-24 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 19:28 [Buildroot] [PATCH 1/1] linux: Don't enable DEVTMPFS support for kernels older than 3.x Ryan Barnett
2014-04-18 19:38 ` Peter Korsgaard
2014-04-18 19:39 ` Thomas Petazzoni
2014-04-22 10:41 ` Luca Ceresoli
2014-04-23 22:45 ` rjbarnet at rockwellcollins.com
2014-04-24 6:49 ` Peter Korsgaard [this message]
2014-04-24 19:47 ` Ryan Barnett
2014-04-24 20:00 ` Peter Korsgaard
2014-04-25 13:09 ` Ryan Barnett
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=87bnvr2ped.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.