From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Karthikeyan Pasupathi <pkarthikeyan1509@gmail.com>,
clg@kaod.org, peter.maydell@linaro.org, andrew@aj.id.au,
joel@jms.id.au, qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] Adding new machine Yosemitev2 in QEMU
Date: Thu, 16 Feb 2023 15:27:56 +0100 [thread overview]
Message-ID: <2e46db2f-d48b-bc6e-85d8-1fa80ef4082c@linaro.org> (raw)
In-Reply-To: <20230216133326.216017-1-pkarthikeyan1509@gmail.com>
On 16/2/23 14:33, Karthikeyan Pasupathi wrote:
> This patch support Yosemitev2 in QEMU environment.
> and introduced EEPROM BMC FRU data support "add fbyv2_bmc_fruid data"
> along with the machine support.
>
>
> Signed-off-by: Karthikeyan Pasupathi <pkarthikeyan1509@gmail.com>
> ---
> hw/arm/aspeed.c | 31 +++++++++++++++++++++++++++++++
> hw/arm/aspeed_eeprom.c | 23 +++++++++++++++++++++++
> hw/arm/aspeed_eeprom.h | 3 +++
> 3 files changed, 57 insertions(+)
> +static void aspeed_machine_yosemitev2_class_init(ObjectClass *oc, void *data)
> +{
> + MachineClass *mc = MACHINE_CLASS(oc);
> + AspeedMachineClass *amc = ASPEED_MACHINE_CLASS(oc);
> +
> + mc->desc = "Facebook YosemiteV2 BMC (ARM1176)";
> + amc->soc_name = "ast2500-a1";
> + amc->hw_strap1 = AST2500_EVB_HW_STRAP1;
> + amc->hw_strap2 = 0;
> + amc->fmc_model = "n25q256a";
> + amc->spi_model = "mx25l25635e";
> + amc->num_cs = 2;
> + amc->i2c_init = yosemitev2_bmc_i2c_init;
> + mc->default_ram_size = 512 * MiB;
Odd indentation
> + mc->default_cpus = mc->min_cpus = mc->max_cpus =
> + aspeed_soc_num_cpus(amc->soc_name);
Here too. What about:
mc->default_cpus = mc->min_cpus = mc->max_cpus
= aspeed_soc_num_cpus(amc->soc_name);
I suppose Cédric can fix when applying, no need for v4.
next prev parent reply other threads:[~2023-02-16 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 13:33 [PATCH v3] Adding new machine Yosemitev2 in QEMU Karthikeyan Pasupathi
2023-02-16 13:50 ` Cédric Le Goater
2023-02-16 14:27 ` Philippe Mathieu-Daudé [this message]
2023-02-16 15:04 ` karthikeyan Pasupathi
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=2e46db2f-d48b-bc6e-85d8-1fa80ef4082c@linaro.org \
--to=philmd@linaro.org \
--cc=andrew@aj.id.au \
--cc=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=pkarthikeyan1509@gmail.com \
--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).