[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZmhYoV4ZrNwmIDS4@tlindgre-MOBL1>
Date: Tue, 11 Jun 2024 17:01:05 +0300
From: Tony Lindgren <tony.lindgren@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Petr Mladek <pmladek@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Tony Lindgren <tony@...mide.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] printk: Track command line console positions to fix
console order
On Tue, Jun 11, 2024 at 04:10:45PM +0300, Andy Shevchenko wrote:
> On Tue, Jun 11, 2024 at 12:56:54PM +0300, Tony Lindgren wrote:
> > On Tue, Jun 11, 2024 at 10:17:11AM +0200, Petr Mladek wrote:
> > > I would expect:
> > >
> > > serial8250:0.0 -> ttyS0
> > > serial8250:0.1 -> ttyS1
> > > serial8250:0.2 -> ttyS2
> > > [...]
> >
> > I believe this would be the situation if you make CONFIG_ACPI is not set
> > in the .config.
>
> This is interesting. So, we still have the DEVNAME differences depending on
> the kernel configuration? OTOH, I can't imagine either how we can get the
> device names more stable as long as some drivers instantiate the platform
> device instead of using 8250 core parts (port, base, core) directly.
Seems we can add translation as needed though. For example, we could add
console=serial8250:0.0 translation to the PNP port. Or console=0x3f8,115200.
Regards,
Tony
Powered by blists - more mailing lists