mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Hugo Villeneuve" <hvilleneuve@dimonoff.com>,
	"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] [v3] serial: 8250: remove obsolete and broken PORT_RSA support
Date: Thu, 22 Oct 2026 15:54:34 +0200	[thread overview]
Message-ID: <0cd9560c-6de5-4744-90a4-ecb613594133@app.fastmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2610220418380.22065@angie.orcam.me.uk>

On Thu, Oct 22, 2026, at 05:34, Maciej W. Rozycki wrote:
> On Wed, 21 Oct 2026, Arnd Bergmann wrote:
>
>> >  Or, to self-correct after a few more mind cycles spent on this piece, the 
>> > region below `port->iobase' is an expansion of one above, where standard 
>> > 8250 registers of the onboard serial port reside.  Which makes even more 
>> > sense, to me anyway.
>> 
>> Good catch, so it should still work the same way it was originally
>> designed, though I think it still requires a modified setserial to
>> set PORT_RSA, or a boot time argument for autoconfiguration with
>> UART_CONFIG_TYPE.
>
>  Well, this is ISA, what do you expect?  We've dropped lots of stuff that 
> required perhaps even more complex manual configuration already (QIC-02 
> tapes, anyone?).

I pointed it out because this is the only UART driver that relies on
that specific mechanism. Everything else uses either hardcoded port
numbers that like the 3f8/2f8/3e8/2e8 ports for PC compatibility or
they rely on PnP. I understand that we have other network/scsi/sound/iio
drivers that also do this.

    Arnd

      reply	other threads:[~2026-10-22 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  8:56 Arnd Bergmann
2026-10-19  9:39 ` Greg Kroah-Hartman
2026-10-19 10:25   ` Andy Shevchenko
2026-10-21  8:50   ` Arnd Bergmann
2026-10-19 10:23 ` Andy Shevchenko
2026-10-19 15:06 ` Jiri Slaby
2026-10-21  3:52 ` Maciej W. Rozycki
2026-10-21  4:07   ` Maciej W. Rozycki
2026-10-21  8:00     ` Arnd Bergmann
2026-10-22  3:34       ` Maciej W. Rozycki
2026-10-22 13:54         ` Arnd Bergmann [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=0cd9560c-6de5-4744-90a4-ecb613594133@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=u.kleine-koenig@baylibre.com \
    /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

all inboxes | Powered by JetHome®