From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Denis Mukhin <dmkhn@proton.me>
Cc: Denis Mukhin <dmukhin@ford.com>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] x86/early_printk: add MMIO-based UARTs
Date: Tue, 8 Apr 2025 11:30:00 +0300 [thread overview]
Message-ID: <Z_TeiDVh50u7OhIw@smile.fi.intel.com> (raw)
In-Reply-To: <vCbvBjUt9kPZhYP0tXAoVKrIn5hk5ON-HEqi2OjnCECThGJ73vh7S4qAKspAlxtgBAHFv1Sc_k6Hmdeq_nYXReITCt2FNRy1wWZR-udke9c=@proton.me>
On Mon, Apr 07, 2025 at 11:04:42PM +0000, Denis Mukhin wrote:
> On Monday, April 7th, 2025 at 9:38 AM, Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> > On Mon, Mar 24, 2025 at 05:55:40PM -0700, Denis Mukhin wrote:
> > > During the bring-up of an x86 board, the kernel was crashing before
> > > reaching the platform's console driver because of a bug in the firmware,
> > > leaving no trace of the boot progress.
> > >
> > > It was discovered that the only available method to debug the kernel
> > > boot process was via the platform's MMIO-based UART, as the board lacked
> > > an I/O port-based UART, PCI UART, or functional video output.
> > >
> > > Then it turned out that earlyprintk= does not have a knob to configure
> > > the MMIO-mapped UART.
> > >
> > > Extend the early printk facility to support platform MMIO-based UARTs
> > > on x86 systems, enabling debugging during the system bring-up phase.
> > >
> > > The command line syntax to enable platform MMIO-based UART is:
> > > earlyprintk=mmio,membase[,{nocfg|baudrate}][,keep]
> > >
> > > Note, the change does not integrate MMIO-based UART support to:
> > > arch/x86/boot/early_serial_console.c
> > >
> > > Also, update kernel parameters documentation with the new syntax and
> > > add missing 'nocfg' setting to PCI serial cards description.
> >
> > Just for your information: Have you seen this rather old series of mine?
> >
> > https://bitbucket.org/andy-shev/linux/commits/branch/topic%2Fx86%2Fboot-earlyprintk
>
> This is a nice cleanup!
> Thanks for sharing.
>
> Sorry, I haven't seen the series above, I had to write a patch (which was months ago).
> It's just I could not post it on the mailing list until recently.
No problem. Can you look at
https://lore.kernel.org/r/20250407172214.792745-1-andriy.shevchenko@linux.intel.com
? I forgot to Cc you and that is an important fix.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-08 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 0:55 [PATCH v3] x86/early_printk: add MMIO-based UARTs Denis Mukhin via B4 Relay
2025-04-07 16:38 ` Andy Shevchenko
2025-04-07 23:04 ` Denis Mukhin
2025-04-08 8:30 ` Andy Shevchenko [this message]
2025-04-08 21:03 ` Denis Mukhin
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=Z_TeiDVh50u7OhIw@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=dmkhn@proton.me \
--cc=dmukhin@ford.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).