From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
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:14:23 +0200 [thread overview]
Message-ID: <cba24059-b3a5-1587-c1f3-8d7dfd0807f5@de.ibm.com> (raw)
In-Reply-To: <20200520070743.GO4974@valentin-vidic.from.hr>
On 20.05.20 09:07, Valentin Vidić wrote:
> 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?
My point was more that a similar issue should happen when installing in LPAR. LPAR
uses the line mode style console which is ttyS0 for the console but sclp_line0 for the
tty. How does the debian installer handle this?
Regarding your patch I fear that this patch would break existing setups so we cannot
use it as is.
next prev parent reply other threads:[~2020-05-20 7:14 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ć
2020-05-20 7:14 ` Christian Borntraeger [this message]
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=cba24059-b3a5-1587-c1f3-8d7dfd0807f5@de.ibm.com \
--to=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 \
--cc=vvidic@valentin-vidic.from.hr \
/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