From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] MIPS: Unify low-level debugging functionalities
Date: Wed, 20 Dec 2023 22:18:14 +0100 [thread overview]
Message-ID: <ZYNaFhFp/+q+/Z0Z@alpha.franken.de> (raw)
In-Reply-To: <20231029-mips_debug_ll-v1-0-d7a491e8c278@flygoat.com>
On Sun, Oct 29, 2023 at 02:53:01AM +0000, Jiaxun Yang wrote:
> The plan is to elimiate platform specific early_printk and
> cps-vec-ns16550 by debug_ll and earlycon.
https://xkcd.com/927/ ?
sorry I don't think that just another new function is good approach.
Doing this will end up with another method for early debugging and
all other will stay.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-12-20 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 2:53 Jiaxun Yang
2023-10-29 2:53 ` [PATCH 1/8] MIPS: asm: Move strings to .rodata.str section Jiaxun Yang
2023-10-29 2:53 ` [PATCH 2/8] MIPS: debug: Implement low-level debugging functions Jiaxun Yang
2023-10-29 2:53 ` [PATCH 3/8] MIPS: debug: Hook up DEBUG_LL with early printk Jiaxun Yang
2023-10-29 2:53 ` [PATCH 4/8] MIPS: debug: Provide an early exception vector for low-level debugging Jiaxun Yang
2023-10-29 2:53 ` [PATCH 5/8] MIPS: debug_ll: Add Kconfig symbols for some 8250 uarts Jiaxun Yang
2023-10-29 2:53 ` [PATCH 6/8] MIPS: debug_ll: Implement support for Alchemy uarts Jiaxun Yang
2023-10-29 2:53 ` [PATCH 7/8] MIPS: debug_ll: Implement support for AR933X uarts Jiaxun Yang
2023-10-29 2:53 ` [PATCH 8/8] MIPS: zboot: Convert to use debug_ll facilities Jiaxun Yang
2023-12-01 11:58 ` [PATCH 0/8] MIPS: Unify low-level debugging functionalities Jiaxun Yang
2023-12-20 21:18 ` Thomas Bogendoerfer [this message]
2023-12-21 1:40 ` Jiaxun Yang
2023-12-21 2:21 ` Jiaxun Yang
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=ZYNaFhFp/+q+/Z0Z@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.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
all inboxes | Powered by JetHome®