From: Willy Tarreau <w@1wt.eu>
To: Borislav Petkov <bp@alien8.de>
Cc: "Guillaume Tucker" <guillaume.tucker@collabora.com>,
"Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Collabora Kernel ML" <kernel@collabora.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Diego Elio Pettenò" <flameeyes@flameeyes.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Nathan Chancellor" <natechancellor@gmail.com>,
kernelci@groups.io
Subject: Re: [PATCH] x86/x86_64_defconfig: Enable the serial console
Date: Mon, 12 Oct 2020 16:40:40 +0200 [thread overview]
Message-ID: <20201012144040.GB11614@1wt.eu> (raw)
In-Reply-To: <20201012143212.GC22829@zn.tnic>
On Mon, Oct 12, 2020 at 04:32:12PM +0200, Borislav Petkov wrote:
> On Mon, Oct 12, 2020 at 11:22:10AM +0100, Guillaume Tucker wrote:
> > However, it was found while adding some x86 Chromebooks[1] to
> > KernelCI that x86_64_defconfig lacked some basic things for
> > anyone to be able to boot a kernel with a serial console enabled
> > on those.
>
> Hold on, those are laptops, right? How come they do have serial console?
> Because laptops don't have serial console - that has been the eternal
> problem with debugging kernels on laptops.
Well, to be precise, they don't have *anymore*. I used to exclusively
select laptops having a serial port given that I was using it daily with
routers, until I had to resign when I abandonned my good old NC8000 :-/
Willy
next prev parent reply other threads:[~2020-10-12 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:22 [PATCH] x86/x86_64_defconfig: Enable the serial console Enric Balletbo i Serra
2020-10-08 16:40 ` Borislav Petkov
2020-10-08 18:31 ` Randy Dunlap
2020-10-11 11:43 ` Enric Balletbo i Serra
2020-10-11 12:20 ` Borislav Petkov
2020-10-11 15:40 ` Enric Balletbo i Serra
2020-10-11 15:57 ` Borislav Petkov
2020-10-11 17:05 ` Enric Balletbo i Serra
2020-10-11 19:06 ` Borislav Petkov
2020-10-12 3:58 ` Willy Tarreau
2020-10-12 10:22 ` Guillaume Tucker
2020-10-12 14:32 ` Borislav Petkov
2020-10-12 14:40 ` Willy Tarreau [this message]
2020-10-12 15:10 ` Guillaume Tucker
2020-10-12 16:43 ` Borislav Petkov
2020-10-12 17:52 ` Nick Desaulniers
2020-10-12 16:39 ` Borislav Petkov
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=20201012144040.GB11614@1wt.eu \
--to=w@1wt.eu \
--cc=bp@alien8.de \
--cc=enric.balletbo@collabora.com \
--cc=flameeyes@flameeyes.com \
--cc=guillaume.tucker@collabora.com \
--cc=hpa@zytor.com \
--cc=kernel@collabora.com \
--cc=kernelci@groups.io \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=rdunlap@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.