[PATCH] xilinx: Enable CMD_NFS for Zynq and Kria platforms

[PATCH] xilinx: Enable CMD_NFS for Zynq and Kria platforms

[Michal Simek via U-Boot]

Enable CMD_NFS for Zynq and Kria platforms to have it available by default.

Signed-off-by: Michal Simek <michal.simek@amd.com>
---

 configs/xilinx_zynq_virt_defconfig   | 1 +
 configs/xilinx_zynqmp_kria_defconfig | 1 +
 2 files changed, 2 insertions(+)

diff --git a/configs/xilinx_zynq_virt_defconfig b/configs/xilinx_zynq_virt_defconfig
index 30ffe28298a0..b7ef9407dcdb 100644
--- a/configs/xilinx_zynq_virt_defconfig
+++ b/configs/xilinx_zynq_virt_defconfig
@@ -69,6 +69,7 @@ CONFIG_CMD_MTD=y
 CONFIG_CMD_NAND_LOCK_UNLOCK=y
 CONFIG_CMD_SF_TEST=y
 CONFIG_CMD_USB=y
+CONFIG_CMD_NFS=y
 CONFIG_CMD_SNTP=y
 CONFIG_CMD_CACHE=y
 CONFIG_CMD_EFIDEBUG=y
diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig
index ba4fdb9d657a..877e6c7f474e 100644
--- a/configs/xilinx_zynqmp_kria_defconfig
+++ b/configs/xilinx_zynqmp_kria_defconfig
@@ -82,6 +82,7 @@ CONFIG_CMD_SDRAM=y
 CONFIG_CMD_SF_TEST=y
 CONFIG_CMD_SPI=y
 CONFIG_CMD_USB=y
+CONFIG_CMD_NFS=y
 CONFIG_CMD_SNTP=y
 CONFIG_WGET_HTTPS=y
 CONFIG_CMD_BMP=y
---
base-commit: da4b763f29446ca22856e0f681076e5d27268c05
branch: debian-sent3

-- 
2.43.0

Re: [PATCH] xilinx: Enable CMD_NFS for Zynq and Kria platforms

[Peter Robinson via U-Boot]

On Wed, 22 Jul 2026 at 13:15, Michal Simek via U-Boot
<u-boot@lists.u-boot-project.org> wrote:
>
> Enable CMD_NFS for Zynq and Kria platforms to have it available by default.

How useful is this these days? From memory it's NFSv2 and that's
mostly dead everywhere.

> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
>  configs/xilinx_zynq_virt_defconfig   | 1 +
>  configs/xilinx_zynqmp_kria_defconfig | 1 +
>  2 files changed, 2 insertions(+)
>
> diff --git a/configs/xilinx_zynq_virt_defconfig b/configs/xilinx_zynq_virt_defconfig
> index 30ffe28298a0..b7ef9407dcdb 100644
> --- a/configs/xilinx_zynq_virt_defconfig
> +++ b/configs/xilinx_zynq_virt_defconfig
> @@ -69,6 +69,7 @@ CONFIG_CMD_MTD=y
>  CONFIG_CMD_NAND_LOCK_UNLOCK=y
>  CONFIG_CMD_SF_TEST=y
>  CONFIG_CMD_USB=y
> +CONFIG_CMD_NFS=y
>  CONFIG_CMD_SNTP=y
>  CONFIG_CMD_CACHE=y
>  CONFIG_CMD_EFIDEBUG=y
> diff --git a/configs/xilinx_zynqmp_kria_defconfig b/configs/xilinx_zynqmp_kria_defconfig
> index ba4fdb9d657a..877e6c7f474e 100644
> --- a/configs/xilinx_zynqmp_kria_defconfig
> +++ b/configs/xilinx_zynqmp_kria_defconfig
> @@ -82,6 +82,7 @@ CONFIG_CMD_SDRAM=y
>  CONFIG_CMD_SF_TEST=y
>  CONFIG_CMD_SPI=y
>  CONFIG_CMD_USB=y
> +CONFIG_CMD_NFS=y
>  CONFIG_CMD_SNTP=y
>  CONFIG_WGET_HTTPS=y
>  CONFIG_CMD_BMP=y
> ---
> base-commit: da4b763f29446ca22856e0f681076e5d27268c05
> branch: debian-sent3
>
> --
> 2.43.0
>

Re: [PATCH] xilinx: Enable CMD_NFS for Zynq and Kria platforms

[Michal Simek via U-Boot]

On 7/22/26 14:26, Peter Robinson wrote:
> On Wed, 22 Jul 2026 at 13:15, Michal Simek via U-Boot
> <u-boot@lists.u-boot-project.org> wrote:
>>
>> Enable CMD_NFS for Zynq and Kria platforms to have it available by default.
> 
> How useful is this these days? From memory it's NFSv2 and that's
> mostly dead everywhere.

That's up to every customer to decide if they want to use it or not. We have it 
in u-boot-xlnx tree from quite a while and we don't know if any customer is 
using it or not but I want to stay as close to mainline as possible hence this 
patch. If this is something what it is supposed to be removed we should remove it.

Cheers,
Michal

Re: [PATCH] xilinx: Enable CMD_NFS for Zynq and Kria platforms

[Peter Robinson via U-Boot]

> >> Enable CMD_NFS for Zynq and Kria platforms to have it available by default.
> >
> > How useful is this these days? From memory it's NFSv2 and that's
> > mostly dead everywhere.
>
> That's up to every customer to decide if they want to use it or not. We have it
> in u-boot-xlnx tree from quite a while and we don't know if any customer is
> using it or not but I want to stay as close to mainline as possible hence this
> patch. If this is something what it is supposed to be removed we should remove it.

That's ultimately why it was disabled by default, those sort of
options are the sort that are there for the customer to enable in
their builds if they need that feature as opposed to something I would
think you'd enable by default on a board. It reduces possible attack
vectors on the devices by default.