From: Bin Meng <bmeng.cn@gmail.com>
To: Nicholas Sielicki <sielicki@yandex.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Cc: Bin Meng <bmeng@tinylab.org>
Subject: [Buildroot] [PATCH] board/intel: galileo: Enable Linux kernel root file system on NFS
Date: Fri, 10 Feb 2023 01:20:02 +0800 [thread overview]
Message-ID: <20230209172002.1442869-1-bmeng.cn@gmail.com> (raw)
From: Bin Meng <bmeng@tinylab.org>
Update linux-3.14.config for Galileo to enable Linux kernel root
file system on NFS.
Signed-off-by: Bin Meng <bmeng@tinylab.org>
---
board/intel/galileo/linux-3.14.config | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/board/intel/galileo/linux-3.14.config b/board/intel/galileo/linux-3.14.config
index e7aa9cf232..c658afb88e 100644
--- a/board/intel/galileo/linux-3.14.config
+++ b/board/intel/galileo/linux-3.14.config
@@ -154,9 +154,9 @@ CONFIG_TUN=y
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_NET_VENDOR_SMSC is not set
-CONFIG_STMMAC_ETH=m
+CONFIG_STMMAC_ETH=y
# CONFIG_STMMAC_PLATFORM is not set
-CONFIG_STMMAC_PCI=m
+CONFIG_STMMAC_PCI=y
# CONFIG_NET_VENDOR_SUN is not set
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
@@ -306,3 +306,6 @@ CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
# CONFIG_VIRTUALIZATION is not set
CONFIG_CRC_T10DIF=y
+CONFIG_NFS_FS=y
+CONFIG_ROOT_NFS=y
+CONFIG_IP_PNP=y
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-02-09 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 17:20 Bin Meng [this message]
2023-08-10 21:02 ` [Buildroot] [PATCH] board/intel: galileo: Enable Linux kernel root file system on NFS Thomas Petazzoni via buildroot
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=20230209172002.1442869-1-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=bmeng@tinylab.org \
--cc=buildroot@buildroot.org \
--cc=sielicki@yandex.com \
--cc=thomas.petazzoni@bootlin.com \
/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