From: Fiona Klute <fiona.klute@gmx.de>
To: Tony Dinh <mibodhi@gmail.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/2] doc: Detailed example for netconsole setup
Date: Thu, 16 May 2024 12:07:02 +0200 [thread overview]
Message-ID: <42513d32-0159-400e-8b83-8404b48ff5ac@gmx.de> (raw)
In-Reply-To: <CAJaLiFxwTCCiXjrRP4eHZ+Enjw+X5H-Yzd6wFJemQnLR6Ws0Rw@mail.gmail.com>
Am 15.05.24 um 21:05 schrieb Tony Dinh:
> Hi Fiona,
>
> On Tue, May 14, 2024 at 5:28 PM Fiona Klute <fiona.klute@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.klute@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
next prev parent reply other threads:[~2024-05-16 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 20:20 [PATCH 1/2] doc: Detailed example for netconsole setup Fiona Klute
2024-05-14 20:20 ` [PATCH 2/2] doc: Update netconsole examples Fiona Klute
2024-05-17 9:09 ` Heinrich Schuchardt
2024-05-15 19:05 ` [PATCH 1/2] doc: Detailed example for netconsole setup Tony Dinh
2024-05-16 10:07 ` Fiona Klute [this message]
2024-05-17 7:32 ` Heinrich Schuchardt
2024-05-18 11:00 ` Fiona Klute
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=42513d32-0159-400e-8b83-8404b48ff5ac@gmx.de \
--to=fiona.klute@gmx.de \
--cc=mibodhi@gmail.com \
--cc=u-boot@lists.denx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).