From: "Pali Rohár" <pali@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Nick Child <nick.child@ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Randy Dunlap <rdunlap@infradead.org>,
Paul Mackerras <paulus@samba.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc: Add support for early debugging via Serial 16550 console
Date: Mon, 22 Aug 2022 17:28:52 +0200 [thread overview]
Message-ID: <20220822152852.y5fjpmjjasbu2wab@pali> (raw)
In-Reply-To: <d12435b4-0caa-ba06-f0a5-8c9268bb8dfd@csgroup.eu>
On Monday 22 August 2022 14:13:30 Christophe Leroy wrote:
> >> CONFIG_PPC_EARLY_DEBUG_16550=y
> >> # CONFIG_PPC_EARLY_DEBUG_MEMCONS is not set
> >> CONFIG_PPC_EARLY_DEBUG_16550_PHYSADDR=
> >> CONFIG_PPC_EARLY_DEBUG_16550_STRIDE=1
> >>
> >> which then causes a kconfig prompt when starting
> >> the build...
> >
> > Cannot we set somehow that PPC_EARLY_DEBUG_16550 would be disabled by
> > default when upgrading defconfig?
>
> The only solution I see is to put it at the end of the list, so that the
> previous default value which is PPC_EARLY_DEBUG_MEMCONS gets selected.
Does it work for all cases? If yes, then it looks like an elegant solution.
next prev parent reply other threads:[~2022-08-22 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 21:12 [PATCH] powerpc: Add support for early debugging via Serial 16550 console Pali Rohár
2022-08-19 22:34 ` Randy Dunlap
2022-08-19 22:38 ` Pali Rohár
2022-08-19 22:43 ` Randy Dunlap
2022-08-22 14:14 ` Christophe Leroy
2022-08-22 14:13 ` Christophe Leroy
2022-08-22 15:28 ` Pali Rohár [this message]
2022-08-22 14:09 ` Christophe Leroy
2022-08-22 14:25 ` Christophe Leroy
2022-08-22 15:33 ` Pali Rohár
2022-08-22 16:21 ` Gabriel Paubert
2022-08-22 23:15 ` [PATCH v2] " Pali Rohár
2022-09-24 12:10 ` Pali Rohár
2022-10-04 13:25 ` Michael Ellerman
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=20220822152852.y5fjpmjjasbu2wab@pali \
--to=pali@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nick.child@ibm.com \
--cc=paulus@samba.org \
--cc=rdunlap@infradead.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).