linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Paul Mackerras <paulus@ozlabs.org>,
	linuxppc-dev@ozlabs.org, Benjamin Herrenschmidt <benh@ozlabs.org>,
	Michael Neuling <mikey@neuling.org>,
	Anton Blanchard <anton@ozlabs.org>
Subject: Re: [PATCH RFC 3/4] powerpc/microwatt: Add early debug UART support for Microwatt
Date: Tue, 12 May 2020 11:57:24 +1000	[thread overview]
Message-ID: <87pnb9c3uj.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200509050340.GD1464954@thinks.paulus.ozlabs.org>

Paul Mackerras <paulus@ozlabs.org> writes:
> Currently microwatt-based SoCs come with a "potato" UART.  This
> adds udbg support for the potato UART, giving us both an early
> debug console, and a runtime console using the hvc-udbg support.

Can y'all get a real UART?

There's more code here than in the platform itself.

cheers

  parent reply	other threads:[~2020-05-12  2:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09  5:01 [PATCH RFC 0/4] Add support for Microwatt-based SoCs Paul Mackerras
2020-05-09  5:02 ` [PATCH RFC 1/4] powerpc/radix: Fix compilation for radix with CONFIG_SMP=n Paul Mackerras
2020-05-09  7:52   ` Nicholas Piggin
2020-05-14  8:26     ` Joel Stanley
2020-05-09  5:02 ` [PATCH RFC 2/4] powerpc: Add Microwatt platform Paul Mackerras
2020-05-09  7:58   ` Nicholas Piggin
2020-05-09  8:36     ` Alistair Popple
2020-05-09  9:10       ` Nicholas Piggin
2020-05-12  1:56   ` Michael Ellerman
2020-05-09  5:03 ` [PATCH RFC 3/4] powerpc/microwatt: Add early debug UART support for Microwatt Paul Mackerras
2020-05-11  7:07   ` Segher Boessenkool
2020-05-12  1:57   ` Michael Ellerman [this message]
2020-05-09  5:04 ` [PATCH RFC 4/4] powerpc/radix: Add support for microwatt's PRTBL SPR Paul Mackerras
2020-05-09  8:02   ` Nicholas Piggin

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=87pnb9c3uj.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@ozlabs.org \
    --cc=benh@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=paulus@ozlabs.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).