From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Niek Linnenbank <nieklinnenbank@gmail.com>
Cc: Beniamino Galvani <b.galvani@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v1 1/4] hw/arm/cubieboard: use ARM Cortex-A8 as the default CPU in machine definition
Date: Mon, 2 Mar 2020 18:54:57 +0100 [thread overview]
Message-ID: <3ad40e56-6afc-6dc2-7e73-41dadb2b7c6b@redhat.com> (raw)
In-Reply-To: <CAFEAcA_xB_dMfcALk6sirmRJyJ0rw7_JPK6aqBoZMxh=wH+d-g@mail.gmail.com>
On 3/2/20 4:32 PM, Peter Maydell wrote:
> On Thu, 27 Feb 2020 at 22:01, Niek Linnenbank <nieklinnenbank@gmail.com> wrote:
>>
>> The Cubieboard is a singleboard computer with an Allwinner A10 System-on-Chip [1].
>> As documented in the Allwinner A10 User Manual V1.5 [2], the SoC has an ARM
>> Cortex-A8 processor. Currently the Cubieboard machine definition specifies the
>> ARM Cortex-A9 in its description and as the default CPU.
>>
>> This patch corrects the Cubieboard machine definition to use the ARM Cortex-A8.
>>
>> [1] http://docs.cubieboard.org/products/start#cubieboard1
>> [2] https://linux-sunxi.org/File:Allwinner_A10_User_manual_V1.5.pdf
>>
>> Signed-off-by: Niek Linnenbank <nieklinnenbank@gmail.com>
>> ---
>> hw/arm/cubieboard.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/arm/cubieboard.c b/hw/arm/cubieboard.c
>> index 089f9a30c1..0195925c73 100644
>> --- a/hw/arm/cubieboard.c
>> +++ b/hw/arm/cubieboard.c
>> @@ -68,8 +68,8 @@ static void cubieboard_init(MachineState *machine)
>>
>> static void cubieboard_machine_init(MachineClass *mc)
>> {
>> - mc->desc = "cubietech cubieboard (Cortex-A9)";
>> - mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a9");
>> + mc->desc = "cubietech cubieboard (Cortex-A8)";
>> + mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a8");
>> mc->init = cubieboard_init;
>> mc->block_default_type = IF_IDE;
>> mc->units_per_default_bus = 1;
>
> This is worth fixing, but I'm pretty sure it doesn't have
> any user-visible effects, because the CPU is created by
> hw/arm/allwinner-a10.c:aw_a10_init(), which always uses
> cortex-a8 regardless of what the user specified on the command
> line or what the mc->default_cpu_type is.
It is worth fixing if we continue the MachineClass code cleanup Igor
wants (moving the ram size / cpu type checks in the machine common code).
>
> Fixes: 8a863c8120994981a099
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> if you tweak the commit message to mention that it
> wasn't a user-visible bug (but I'll do that myself if there
> isn't anything else in the series that means it needs a respin).
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2020-03-02 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 22:01 [PATCH v1 0/4] hw/arm/cubieboard: correct CPU type and add machine argument checks Niek Linnenbank
2020-02-27 22:01 ` [PATCH v1 1/4] hw/arm/cubieboard: use ARM Cortex-A8 as the default CPU in machine definition Niek Linnenbank
2020-03-02 15:32 ` Peter Maydell
2020-03-02 17:54 ` Philippe Mathieu-Daudé [this message]
2020-02-27 22:01 ` [PATCH v1 2/4] hw/arm/cubieboard: restrict allowed CPU type to ARM Cortex-A8 Niek Linnenbank
2020-03-02 15:33 ` Peter Maydell
2020-02-27 22:01 ` [PATCH v1 3/4] hw/arm/cubieboard: restrict allowed RAM size to 512MiB and 1GiB Niek Linnenbank
2020-03-02 15:41 ` Peter Maydell
2020-02-27 22:01 ` [PATCH v1 4/4] hw/arm/cubieboard: report error when using unsupported -bios argument Niek Linnenbank
2020-03-02 15:44 ` Peter Maydell
2020-03-02 18:04 ` Philippe Mathieu-Daudé
2020-03-02 22:30 ` Niek Linnenbank
2020-03-02 16:06 ` [PATCH v1 0/4] hw/arm/cubieboard: correct CPU type and add machine argument checks Peter Maydell
2020-03-02 22:21 ` Niek Linnenbank
2020-03-02 18:05 ` Philippe Mathieu-Daudé
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=3ad40e56-6afc-6dc2-7e73-41dadb2b7c6b@redhat.com \
--to=philmd@redhat.com \
--cc=b.galvani@gmail.com \
--cc=nieklinnenbank@gmail.com \
--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).