[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cba24059-b3a5-1587-c1f3-8d7dfd0807f5@de.ibm.com>
Date: Wed, 20 May 2020 09:14:23 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Valentin Vidić <vvidic@...entin-vidic.from.hr>
Cc: Heiko Carstens <heiko.carstens@...ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] s390/sclp_vt220: Fix console name to match device
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.
Powered by blists - more mailing lists