public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] s390/sclp_vt220: Fix console name to match device
Date: Wed, 20 May 2020 09:07:43 +0200	[thread overview]
Message-ID: <20200520070743.GO4974@valentin-vidic.from.hr> (raw)
In-Reply-To: <65218cdb-d03f-29a8-1e78-42ff2d4f958d@de.ibm.com>

On Wed, May 20, 2020 at 07:25:06AM +0200, Christian Borntraeger wrote:
> This is not as simple. ttyS1 is the the console name and ttysclp0 is the tty name.
> This has mostly historic reasons and it obviously causes problems.
> But there is  documentation out that that actually describes the use of 
> console=ttyS1 console=ttyS0.
> to have console output on both sclp consoles and there are probably scripts
> using ttyS1.
> 
> I am wondering. The tty for ttyS0 is named sclp_line0. Does this work in LPAR?

I ran into this problem with qemu-system-s390x, so not sure about LPAR.
Would changing the tty name also cause problems?

-- 
Valentin

  reply	other threads:[~2020-05-20  7:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 18:16 [PATCH] s390/sclp_vt220: Fix console name to match device Valentin Vidic
2020-05-20  5:25 ` Christian Borntraeger
2020-05-20  7:07   ` Valentin Vidić [this message]
2020-05-20  7:14     ` Christian Borntraeger
2020-05-20  8:04       ` Valentin Vidić
2021-04-27 19:40 ` [PATCH v2] " Valentin Vidic
2021-04-28 12:39   ` Christian Borntraeger
2021-04-28 13:38   ` Hendrik Brueckner
2021-04-28 14:44     ` Christian Borntraeger
2021-04-28 16:13     ` Valentin Vidić

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=20200520070743.GO4974@valentin-vidic.from.hr \
    --to=vvidic@valentin-vidic.from.hr \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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