Am 15.05.24 um 21:05 schrieb Tony Dinh:
Hi Fiona,
On Tue, May 14, 2024 at 5:28 PM Fiona Klute <fiona.kl...@gmx.de> wrote:
This adds details that I would have liked to have readily available,
in particular how to activate the network interface before enabling
netconsole, and how to integrate netconsole so you can use the U-Boot
prompt.
Signed-off-by: Fiona Klute <fiona.kl...@gmx.de>
---
doc/usage/netconsole.rst | 33 ++++++++++++++++++++++++++++++++-
1 file changed, 32 insertions(+), 1 deletion(-)
diff --git a/doc/usage/netconsole.rst b/doc/usage/netconsole.rst
index 2aa3b9ccc5..0c983e6970 100644
--- a/doc/usage/netconsole.rst
+++ b/doc/usage/netconsole.rst
@@ -18,7 +18,9 @@ broadcast address and port 6666 are used. If it is set to an
IP
address of 0 (or 0.0.0.0) then no messages are sent to the network.
The source / listening port can be configured separately by setting
the 'ncinport' environment variable and the destination port can be
-configured by setting the 'ncoutport' environment variable.
+configured by setting the 'ncoutport' environment variable. Note that
+you need to set up the network interface (e.g. using DHCP) before it
+can be used for network console.
For example, if your server IP is 192.168.1.1, you could use::
@@ -107,3 +109,32 @@ as follows:
Note that unlike the U-Boot implementation the Linux netconsole is
unidirectional, i. e. you have console output only in Linux.
+
+Setup via environment
+---------------------
+
+If persistent environment is enabled in your U-Boot configuration, you
+can configure the network console using the environment. For example::
+
+ => env set autoload no
+ => env set hostname "u-boot"
+ => env set bootdelay 5
+ => env set nc 'dhcp; env set stdout nc; env set stdin nc'
We would need "env set stderr nc" here, too.
Thanks, I guess I should add that to the existing description and
example as well then. I'll test it and then send an update.
Best regards,
Fiona
