From: Nicholas Piggin <npiggin@gmail.com>
To: Anton Blanchard <anton@ozlabs.org>,
Benjamin Herrenschmidt <benh@ozlabs.org>,
linuxppc-dev@ozlabs.org, Michael Neuling <mikey@neuling.org>,
Paul Mackerras <paulus@ozlabs.org>
Cc: Alistair Popple <alistair@popple.id.au>
Subject: Re: [PATCH RFC 2/4] powerpc: Add Microwatt platform
Date: Sat, 09 May 2020 17:58:57 +1000 [thread overview]
Message-ID: <1589010752.ygtog0nhjc.astroid@bobo.none> (raw)
In-Reply-To: <20200509050255.GC1464954@thinks.paulus.ozlabs.org>
Excerpts from Paul Mackerras's message of May 9, 2020 3:02 pm:
> Microwatt is a FPGA-based implementation of the Power ISA. It
> currently only implements little-endian 64-bit mode, and does
> not (yet) support SMP.
>
> This adds a new machine type to support FPGA-based SoCs with a
> Microwatt core.
Very cool!
Would there be any point sharing this with the "naked metal" platform
Alistair has for booting POWER in L3 without OPAL? Or is it easy enough
to have a several different simple 64s platforms?
I have an HPT conditional compile patch and a few other diet Kconfig
things I'll now be better justified to try get merged :)
Thanks,
Nick
next prev parent reply other threads:[~2020-05-09 8:01 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 [this message]
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
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=1589010752.ygtog0nhjc.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=alistair@popple.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 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.