From: Jeremy Kerr <jk@ozlabs.org>
To: Andrew Jeffery <andrew@aj.id.au>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
qemu-arm@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 0/4] Add ASPEED AST2400 SoC and OpenPower BMC machine
Date: Tue, 15 Mar 2016 12:34:42 +0800 [thread overview]
Message-ID: <56E790E2.7040006@ozlabs.org> (raw)
In-Reply-To: <1457928832-31026-1-git-send-email-andrew@aj.id.au>
Hi Andrew,
> This patch series models enough of the ASPEED AST2400 ARM9 SoC[0] to
> boot an aspeed_defconfig Linux kernel[1][2]. Specifically, the series
> implements the ASPEED timer and VIC devices, integrates them into an
> AST2400 SoC and exposes it all through a new opbmc2400 machine. The
> device model patches only partially implement the hardware features of
> the timer and VIC, again mostly just enough to boot Linux.
Awesome! Nice to have these patches escaping the lab :)
In terms of naming suggestions: I think this depends on what we're
looking to emulate here. I see two options:
The qemu platform becomes a "reference" for OpenPOWER bmc hardware, but
doesn't necessarily align with an actual machine. In that case,
something generic like opbmc-<SoC> would make sense.
On the other hand, if we'd like to create qemu platforms that represent
actual machines (eg, the OpenPOWER "palmetto" machine), then
<PLATFORM>-bmc would seem more appropriate. In this case, the machine
name would be palmetto-bmc. No need to include the SoC name in that, as
it's defined by the hardware implementation.
I think the latter option may be more generally useful.
Regards,
Jeremy
next prev parent reply other threads:[~2016-03-15 4:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 4:13 [Qemu-devel] [PATCH v4 0/4] Add ASPEED AST2400 SoC and OpenPower BMC machine Andrew Jeffery
2016-03-14 4:13 ` [Qemu-devel] [PATCH v4 1/4] hw/timer: Add ASPEED timer device model Andrew Jeffery
2016-03-15 13:14 ` Cédric Le Goater
2016-03-15 23:06 ` Andrew Jeffery
2016-03-15 18:14 ` Dmitry Osipenko
2016-03-15 22:48 ` Andrew Jeffery
2016-03-14 4:13 ` [Qemu-devel] [PATCH v4 2/4] hw/intc: Add (new) ASPEED VIC " Andrew Jeffery
2016-03-14 4:13 ` [Qemu-devel] [PATCH v4 3/4] hw/arm: Add ASPEED AST2400 SoC model Andrew Jeffery
2016-03-14 4:13 ` [Qemu-devel] [PATCH v4 4/4] hw/arm: Add opbmc2400, an AST2400 OpenPOWER BMC machine Andrew Jeffery
2016-03-15 4:34 ` Jeremy Kerr [this message]
2016-03-15 5:01 ` [Qemu-devel] [PATCH v4 0/4] Add ASPEED AST2400 SoC and OpenPower " Andrew Jeffery
2016-03-15 10:25 ` Cédric Le Goater
2016-03-15 23:09 ` Andrew Jeffery
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=56E790E2.7040006@ozlabs.org \
--to=jk@ozlabs.org \
--cc=aik@ozlabs.ru \
--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).