From: Jack Wang <163wangjack@gmail.com>
To: kchiu@axiado.com
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
Kuan-Jui Chiu <kchiu@axiado.com>
Subject: Re: [PATCH v1 4/5] hw/arm: Add Axiado SoC AX3005
Date: Sun, 23 Aug 2026 18:33:01 +0800 [thread overview]
Message-ID: <E7312F05-0DFD-4501-A59E-1DAD8C999785@gmail.com> (raw)
In-Reply-To: <20260820102132.361642-5-kchiu@axiado.com>
Hi Kuan-Jui
I tested this series with ax3005-evb machine,the initialization did not complete.
The process showed it repeatedly executing in 'ax3005_init'
> +static const TypeInfo ax3005_soc_types[] = {
> + {
> + .name = TYPE_AX3005_SOC,
> + .parent = TYPE_SYS_BUS_DEVICE,
> + .instance_size = sizeof(Ax3005SoCState),
> + .instance_init = ax3005_init,
> + .class_init = ax3005_class_init,
> + }
> +};
You add instance_size here but forget to add class_size. Then qemu defaultly use SysBusDeviceClass’s class_size cause of father-son relationship.
> +typedef struct Ax3005SoCClass {
> + SysBusDeviceClass parent;
> +
> + uint32_t num_cpus;
> +} Ax3005SoCClass;
Here your struct apparently extend SysBusDeviceClass field. I think it is the way why previous repeating behavior.After add class_size locally and rebuild the the machine completed initialization and responded to QMP commands successfully.
Best regards :)
Jack Wang
next prev parent reply other threads:[~2026-08-23 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 10:21 [PATCH v1 0/5] Add Axiado SoC AX3005 and EVB Kuan-Jui Chiu
2026-08-20 10:21 ` [PATCH v1 1/5] hw/sd/axiado_sdhci: Add header guard Kuan-Jui Chiu
2026-08-20 10:21 ` [PATCH v1 2/5] hw/arm: Rename ax3000-boards as axiado-boards Kuan-Jui Chiu
2026-08-20 10:21 ` [PATCH v1 3/5] hw/arm/ax3000: Specify SoC name in header and variable Kuan-Jui Chiu
2026-08-20 10:21 ` [PATCH v1 4/5] hw/arm: Add Axiado SoC AX3005 Kuan-Jui Chiu
2026-08-23 10:33 ` Jack Wang [this message]
2026-08-24 1:50 ` Kuan-Jui Chiu
2026-08-24 12:07 ` Jack Wang
2026-08-20 10:21 ` [PATCH v1 5/5] hw/arm: Add Axiado Ax3005 EVB Kuan-Jui Chiu
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=E7312F05-0DFD-4501-A59E-1DAD8C999785@gmail.com \
--to=163wangjack@gmail.com \
--cc=kchiu@axiado.com \
--cc=peter.maydell@linaro.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 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.