From: Borislav Petkov <bp@alien8.de>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: "Willy Tarreau" <w@1wt.eu>,
"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:32:12 +0200 [thread overview]
Message-ID: <20201012143212.GC22829@zn.tnic> (raw)
In-Reply-To: <b188f977-b11e-f570-599a-7bcf364be0fd@collabora.com>
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. Or do they do some sort of
serial over USB emulation and this is something which only chromebooks
have?
Or is that how it is done:
https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/serial-debugging-howto
?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-12 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201008162206.862203-1-enric.balletbo@collabora.com>
[not found] ` <20201008164044.GE5505@zn.tnic>
[not found] ` <4162cfa4-7bf2-3e6e-1b8c-e19187e6fa10@infradead.org>
[not found] ` <2538da14-0f4b-5d4a-c7bf-6fdb46ba2796@collabora.com>
[not found] ` <20201011122020.GA15925@zn.tnic>
[not found] ` <107a6fb0-a667-2f30-d1f4-640e3fee193a@collabora.com>
[not found] ` <20201011155754.GC15925@zn.tnic>
[not found] ` <1dfdf163-9b54-ceae-b178-c566e6109263@collabora.com>
[not found] ` <20201012035846.GB11282@1wt.eu>
2020-10-12 10:22 ` [PATCH] x86/x86_64_defconfig: Enable the serial console Guillaume Tucker
2020-10-12 14:32 ` Borislav Petkov [this message]
2020-10-12 14:40 ` Willy Tarreau
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=20201012143212.GC22829@zn.tnic \
--to=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=w@1wt.eu \
--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).