From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Mon, 01 Dec 2014 11:34:52 +0100 Subject: [Buildroot] [PATCH v3] Add a defconfig for MIPS Creator CI20 In-Reply-To: <547C4367.2070207@imgtec.com> (Vicente Olivert Riera's message of "Mon, 1 Dec 2014 10:31:03 +0000") References: <1417193009-65132-1-git-send-email-Vincent.Riera@imgtec.com> <87wq6ejtsz.fsf@dell.be.48ers.dk> <547C3F7B.3060804@imgtec.com> <87zjb7hdud.fsf@dell.be.48ers.dk> <547C4367.2070207@imgtec.com> Message-ID: <87vblvhd4j.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Vicente" == Vicente Olivert Riera 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