Djam/u-boot
1
0
Fork 0
mirror of https://github.com/u-boot/u-boot.git synced 2025-04-24 06:24:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Update netconsole examples, mention stderr

Browse source 
Stderr was missing from the initial description and example.

As I understand the env command documentation the subcommand style is
preferred, though the old format is still fully supported.

Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Reviewed-by: Tony Dinh <mibodhi@gmail.com>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
This commit is contained in:
Fiona Klute 2024-05-18 12:47:06 +02:00 • committed by Heinrich Schuchardt
parent 5a116726cf
commit 7c53182e52
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/usage/netconsole.rst
View file

@ -3,10 +3,10 @@ Network console
In U-Boot, we implemented the networked console via the standard In U-Boot, we implemented the networked console via the standard
"devices" mechanism, which means that you can switch between the "devices" mechanism, which means that you can switch between the
serial and network input/output devices by adjusting the 'stdin' and serial and network input/output devices by adjusting the 'stdin',
'stdout' environment variables. To switch to the networked console, 'stdout', and 'stderr' environment variables. To switch to the
set either of these variables to "nc". Input and output can be networked console, set either of these variables to "nc". Input and
switched independently. output can be switched independently.
The default buffer size can be overridden by setting The default buffer size can be overridden by setting
CFG_NETCONSOLE_BUFFER_SIZE. CFG_NETCONSOLE_BUFFER_SIZE.
@ -22,12 +22,14 @@ configured by setting the 'ncoutport' environment variable. Note that
you need to set up the network interface (e.g. using DHCP) before it you need to set up the network interface (e.g. using DHCP) before it
can be used for network console. can be used for network console.
For example, if your server IP is 192.168.1.1, you could use:: For example, if your server IP is 192.168.1.1, you could use:
=> setenv nc 'setenv stdout nc;setenv stdin nc' .. prompt:: bash =>
=> setenv ncip 192.168.1.1
=> saveenv env set nc 'env set stdout nc; env set stderr nc; env set stdin nc'
=> run nc env set ncip '192.168.1.1'
env save
run nc
On the host side, please use this script to access the console On the host side, please use this script to access the console