From: Joel Stanley <joel@jms.id.au>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>, "Cédric Le Goater" <clg@kaod.org>,
"Cameron Esfahani via" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] aspeed: Emulate the AST2600A3
Date: Tue, 13 Apr 2021 02:27:52 +0000 [thread overview]
Message-ID: <CACPK8XdD7xMM-ncxZG7i7QZdpJSvSPVLgSCX+tCgf2g1=Ctx-Q@mail.gmail.com> (raw)
In-Reply-To: <66ef55f5-de03-46b1-ada0-089246e0dad1@www.fastmail.com>
On Mon, 12 Apr 2021 at 22:57, Andrew Jeffery <andrew@aj.id.au> wrote:
>
>
>
> On Tue, 13 Apr 2021, at 00:57, Cédric Le Goater wrote:
> > On 3/4/21 1:43 PM, Joel Stanley wrote:
> > > This is the latest revision of the ASPEED 2600 SoC.
> >
> > Should we change all machines to use the new SoC ?
> >
> > I would prefer if we introduced an "ast2600-a3" Aspeed SoC, that we would
> > use for the newer rainier machine, and leave the tacoma-bmc and ast2600-evb
> > machines as they are.
>
> I think we just change them all. We're not going to see pre-A3 chips in
> production systems.
We should split this patch into two. The A3 support is not yet present
in any u-boot tree, so it would be premature to update any socs to
emulate the A3. We can expect support in the coming months, and when
that lands we can consider updating.
However filling out some of the clock register reset values is
important for guests to calculate sensible clock rates, so we should
do that now for the A1.
Cheers,
Joel
prev parent reply other threads:[~2021-04-13 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 12:43 [PATCH] aspeed: Emulate the AST2600A3 Joel Stanley
2021-03-04 13:32 ` Philippe Mathieu-Daudé
2021-04-12 15:27 ` Cédric Le Goater
2021-04-12 22:56 ` Andrew Jeffery
2021-04-13 2:27 ` Joel Stanley [this message]
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='CACPK8XdD7xMM-ncxZG7i7QZdpJSvSPVLgSCX+tCgf2g1=Ctx-Q@mail.gmail.com' \
--to=joel@jms.id.au \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).