[SLOF] [PATCH] Mention the CR vs. LF problem in the documentation
aik at ozlabs.ru
Wed Sep 1 18:39:24 AEST 2021
On 01/09/2021 18:29, Thomas Huth wrote:
> Let's hope that this will help to avoid that people run into the same
> problem again in the future. At least we've got some lines of documentation
> this way where we can point people to who try to use "nc" without "-C".
> Signed-off-by: Thomas Huth <thuth at redhat.com>
> README | 11 +++++++++++
> 1 file changed, 11 insertions(+)
> diff --git a/README b/README
> index 203797b..1b6d5bf 100644
> --- a/README
> +++ b/README
> @@ -266,6 +266,17 @@ New assembly code submitted to SLOF should follow the coding style
> guidelines for the Linux kernel , i.e. indent with tabs, not with spaces.
> +6.0 Tips and tricks
> +- Note that the serial console support is written with serial terminals in
> + mind. Thus SLOF only looks for CR (0x0d) characters as line endings at the
> + command prompt. If you want to connect to the console with a program like
> + "ncat" for example, you have to make sure that it indeed sends CR characters
> + instead of plain LF (0x0a) characters. For ncat that means that you have to
> + use "nc -C ..." to enable the CR-LF mode.
We rather want "stty raw && nc ..." ("nc" without -C) as this is closer
to what terminal + QEMU do.
More information about the SLOF