Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: "linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v3 0/9] MIPS: Unify low-level debugging functionalities
Date: Wed, 22 May 2024 09:28:22 +0100	[thread overview]
Message-ID: <13aa508f-6830-4d52-87fd-5063f737c990@app.fastmail.com> (raw)
In-Reply-To: <Zk2mt/FsgltvhVzf@alpha.franken.de>



在2024年5月22日五月 上午9:03,Thomas Bogendoerfer写道:
[...]
>
> hmmm, I thought I was clear enough on version 1 of this series.
>
> I don't want an additional printk like debug interface, There is
> prom_putchar() and early printk console, which always got me past
> any boot issue.

So it's not an additional printk like debug interface, it actually
merged 3 existing debug interfaces, the first being zboot's assembly
print routines, the second being CPS's assembly print routines, the
third being some platform specific early printk. I think they are
all essential for debugging early faults, for zboot that's the only
way to print something at decompressing stage, for CPS as other cores
are booting in non-coherent state we can't safely use any kernel
functions, for early_printk that can help us *reduce* the amount
of early printk code by just adding UART base to config.

The only thing being added is the ability to debug very early exception,
even that is partially ported from existing CPS assembly debugging routines.

Please let me know your thoughts.

Thanks
>
> Thomas.
>
> -- 
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea.                                                [ RFC1925, 2.3 ]

-- 
- Jiaxun

  reply	other threads:[~2024-05-22  8:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02  9:59 [PATCH v3 0/9] MIPS: Unify low-level debugging functionalities Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 1/9] MIPS: asm: Move strings to .rodata.str section Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 2/9] MIPS: debug: Implement low-level debugging functions Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 3/9] MIPS: debug: Hook up DEBUG_LL with early printk Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 4/9] MIPS: debug: Provide an early exception vector for low-level debugging Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 5/9] MIPS: debug_ll: Add Kconfig symbols for some 8250 uarts Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 6/9] MIPS: debug_ll: Implement support for Alchemy uarts Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 7/9] MIPS: debug_ll: Implement support for AR933X uarts Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 8/9] MIPS: zboot: Convert to use debug_ll facilities Jiaxun Yang
2024-05-02  9:59 ` [PATCH v3 9/9] MIPS: CPS: " Jiaxun Yang
2024-05-15 21:28 ` [PATCH v3 0/9] MIPS: Unify low-level debugging functionalities Jiaxun Yang
2024-05-22  7:15   ` Jiaxun Yang
2024-05-22  8:03     ` Thomas Bogendoerfer
2024-05-22  8:28       ` Jiaxun Yang [this message]
2024-05-22 15:07         ` Jiaxun Yang
2024-05-26 12:44           ` Maciej W. Rozycki
2024-05-26 15:02             ` 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=13aa508f-6830-4d52-87fd-5063f737c990@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=philmd@linaro.org \
    --cc=tsbogend@alpha.franken.de \
    /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