All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: u-boot@lists.denx.de, Angelo Dureghello <angelo@kernel-space.org>
Subject: Re: [PATCH v2 2/3] m68k: m680x0: Initialise the debug uart
Date: Tue, 10 Mar 2026 13:58:43 +0800	[thread overview]
Message-ID: <aa-zE7bNzY8wguoi@google.com> (raw)
In-Reply-To: <20260309105110.672832-2-daniel@0x0f.com>

+Cc Angelo since this touches arch/m68k/

On Mon, Mar 09, 2026 at 07:51:09PM +0900, Daniel Palmer wrote:
> Once the stack is ready we can init the debug uart to help
> with debugging so do that.
> 
> Signed-off-by: Daniel Palmer <daniel@0x0f.com>
> ---
>  arch/m68k/cpu/m680x0/start.S | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/m68k/cpu/m680x0/start.S b/arch/m68k/cpu/m680x0/start.S
> index 0802ca1fca2c..fdfcd66f7785 100644
> --- a/arch/m68k/cpu/m680x0/start.S
> +++ b/arch/m68k/cpu/m680x0/start.S
> @@ -42,6 +42,11 @@ ENTRY(_start)
>  	/* Setup initial stack pointer */
>  	move.l	#CFG_SYS_INIT_SP_ADDR, %sp
>  
> +	/* Setup the debug uart if enabled */
> +#ifdef CONFIG_DEBUG_UART
> +	bsr.l	debug_uart_init
> +#endif
> +
>  	/*
>  	 * Allocate Global Data (GD)
>  	 * board_init_f_alloc_reserve(top) returns the new top of stack in %d0
> -- 
> 2.51.0
> 

  reply	other threads:[~2026-03-10  8:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 10:51 [PATCH v2 1/3] serial: goldfish: Add debug uart support Daniel Palmer
2026-03-09 10:51 ` [PATCH v2 2/3] m68k: m680x0: Initialise the debug uart Daniel Palmer
2026-03-10  5:58   ` Kuan-Wei Chiu [this message]
2026-03-10  8:31     ` Angelo Dureghello
2026-04-12 17:57     ` Angelo Dureghello
2026-03-09 10:51 ` [PATCH v2 3/3] doc: board: virt: m68k: Detail how to use " Daniel Palmer
2026-03-10  6:07 ` [PATCH v2 1/3] serial: goldfish: Add debug uart support Kuan-Wei Chiu
2026-03-10 16:25   ` Tom Rini
2026-03-11  4:08     ` Kuan-Wei Chiu
2026-04-15  0:40 ` Tom Rini

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=aa-zE7bNzY8wguoi@google.com \
    --to=visitorckw@gmail.com \
    --cc=angelo@kernel-space.org \
    --cc=daniel@0x0f.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.