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 18:43:08 +0200 [thread overview]
Message-ID: <20201012164308.GF22829@zn.tnic> (raw)
In-Reply-To: <a165781d-d1c8-04e2-0b60-8d776a21a625@collabora.com>
On Mon, Oct 12, 2020 at 04:10:45PM +0100, Guillaume Tucker wrote:
> You can get serial console on recent enough Chromebooks with a
> debug interface such as SuzyQable:
>
> https://www.sparkfun.com/products/14746
>
> It's not a USB Type-C adapter, it has a debug interface which
> works with Chromebooks that support Case-Closed Debugging.
> Anyone can do that without modifying the Chromebook, and with a
> bit of patience to go through the documentation[1]...
>
> The KernelCI sample results from my previous email were run using
> just that: off-the-shelf Chromebooks + SuzyQ + rebuilt firmware
> for interactive console and tftp boot + kernel with the config
> options in Enric's patch.
That sounds interesting, thanks for elaborating.
At the same time, you see how this setup is very hw-specific and not
really common and those options do not really belong in a defconfig but
in a kernelCI snippet, I'd say.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-10-12 16:43 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
2020-10-12 15:10 ` Guillaume Tucker
2020-10-12 16:43 ` Borislav Petkov [this message]
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=20201012164308.GF22829@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