From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Add a defconfig for MIPS Creator CI20
Date: Mon, 01 Dec 2014 11:34:52 +0100 [thread overview]
Message-ID: <87vblvhd4j.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <547C4367.2070207@imgtec.com> (Vicente Olivert Riera's message of "Mon, 1 Dec 2014 10:31:03 +0000")
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
Hi,
>> >> Is mdev in any way required? We normally only enable the basic stuff
>> >> needed to get a booting system in the defconfigs.
>>
>> > I have added mdev to the defconfig in order to get it working out of the
>> > box, because the kernel defconfig we are using doesn't have
>> > DEVTMPFS_MOUNT support, so if you rely on the default /dev management
>> > option (Dynamic using devtmpfs only) it will not work.
>>
>> But when you build a kernel with Buildroot it will automatically enable
>> DEVTMPFS_MOUNT when needed (E.G. when the system isn't configured for a
>> static /dev), so that shouldn't be an issue?
> I didn't know that. So, if you are using a custom defconfig to build the
> kernel, will Buildroot do more modifications depending on which /dev
> management you have selected? Will not respect your defconfig?
Exactly: We do some minimal config tweaks to ensure you have a working
setup. See the logic in linux/linux.mk (LINUX_CONFIGURE_CMDS).
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2014-12-01 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 16:43 [Buildroot] [PATCH v3] Add a defconfig for MIPS Creator CI20 Vicente Olivert Riera
2014-11-29 8:27 ` Peter Korsgaard
2014-12-01 10:14 ` Vicente Olivert Riera
2014-12-01 10:19 ` Peter Korsgaard
2014-12-01 10:31 ` Vicente Olivert Riera
2014-12-01 10:34 ` Peter Korsgaard [this message]
2014-12-01 14:05 ` Vicente Olivert Riera
2014-12-01 14:13 ` Peter Korsgaard
2014-12-01 14:28 ` Vicente Olivert Riera
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=87vblvhd4j.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox