public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: forbid 8250 on s390
Date: Tue, 12 Dec 2017 18:50:47 +0100	[thread overview]
Message-ID: <cc32ef2c-e940-cfd6-e2e7-f83d013951ea@de.ibm.com> (raw)
In-Reply-To: <20171212155032.2d5ece72@alans-desktop>



On 12/12/2017 04:50 PM, Alan Cox wrote:
> On Tue, 12 Dec 2017 09:08:35 +0100
> Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> 
>> Using "make kvmconfig" results in a potentially unusable linux image
>> on s390.  The reason is that both the (default on s390) sclp consoles
>> as well as the 8250 console register a ttyS<x> as console. Since there
>> will be no 8250 on s390 let's fence 8250. This will ensure that there
>> is always a working sclp console.
> 
> And there is no physical way to attach a PCI express UART to a 390 ?

There is (some sort of) PCI but these cards are packaged in ibm specific I/O cages.
So someone would need to apply some some serious hardware and firmware hacking (since
only IBM-approved PCi cards are allowed) and you would need to have an MSI-capable
8250 as well as an MSI capable driver. (we only support MSI, no classic interrupts)
In addition to that that 8250 probably needs to support virtual functions since we always
run with LPARs.
And even if we can solve all these issues I would say it really does not make any sense at
all, while the current situation obviously breaks the use case "make kvmconfig"

So unless IBM sees some serious business case for 8250, I am inclined to answer you
question with "no" :-)

      reply	other threads:[~2017-12-12 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12  8:08 [PATCH] serial: forbid 8250 on s390 Christian Borntraeger
2017-12-12  8:48 ` Greg Kroah-Hartman
2017-12-12  8:56   ` Christian Borntraeger
2017-12-12 15:50 ` Alan Cox
2017-12-12 17:50   ` Christian Borntraeger [this message]

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=cc32ef2c-e940-cfd6-e2e7-f83d013951ea@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-serial@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