From: Daniel Schultz <d.schultz@phytec.de>
To: <ggiordano@phytec.com>, <w.egorov@phytec.de>,
<trini@konsulko.com>, <u-boot@lists.denx.de>,
<joe.hershberger@ni.com>
Cc: <d.schultz@phytec.de>, <bb@ti.com>, <nmorrisson@phytec.com>,
<upstream@lists.phytec.de>
Subject: [PATCH 2/3] include: env: phytec: k3_net: Use get_cmd
Date: Mon, 28 Apr 2025 07:49:03 -0700 [thread overview]
Message-ID: <20250428144904.1058574-2-d.schultz@phytec.de> (raw)
In-Reply-To: <20250428144904.1058574-1-d.schultz@phytec.de>
'net_fetch_cmd' is not defined by the K3 board files. They
use the more common 'get_cmd' from NXP products.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
---
include/env/phytec/k3_net.env | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/env/phytec/k3_net.env b/include/env/phytec/k3_net.env
index 2ccdc9eaa59..4d5c703cae9 100644
--- a/include/env/phytec/k3_net.env
+++ b/include/env/phytec/k3_net.env
@@ -10,8 +10,8 @@
netargs=setenv bootargs console=${console} root=/dev/nfs ip=dhcp rw
nfsroot=${serverip}:${nfsroot},vers=4,tcp ${optargs}
-netloadimage=${net_fetch_cmd} ${kernel_addr_r} ${serverip}:/Image
-netloadfdt=${net_fetch_cmd} ${fdt_addr_r} ${serverip}:/${fdtfile}
+netloadimage=${get_cmd} ${kernel_addr_r} ${serverip}:/Image
+netloadfdt=${get_cmd} ${fdt_addr_r} ${serverip}:/${fdtfile}
netboot=run netargs;
setenv autoload no;
dhcp;
--
2.25.1
next prev parent reply other threads:[~2025-04-28 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 14:49 [PATCH 1/3] include: env: phytec: k3_net: Remove net_apply_extensions Daniel Schultz
2025-04-28 14:49 ` Daniel Schultz [this message]
2025-04-28 14:49 ` [PATCH 3/3] board: phytec: phycore_am62ax: Update Environment Daniel Schultz
2025-04-28 16:10 ` Tom Rini
2025-04-29 12:14 ` Daniel Schultz
2025-04-29 14:17 ` Tom Rini
2025-05-07 15:24 ` [PATCH 1/3] include: env: phytec: k3_net: Remove net_apply_extensions Tom Rini
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=20250428144904.1058574-2-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=bb@ti.com \
--cc=ggiordano@phytec.com \
--cc=joe.hershberger@ni.com \
--cc=nmorrisson@phytec.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
/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