From: "Cédric Le Goater" <clg@kaod.org>
To: Peter Delevoryas <pdel@fb.com>
Cc: "patrick@stwcx.xyz" <patrick@stwcx.xyz>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v2 1/1] hw/arm/aspeed: Add fby35 machine type
Date: Fri, 6 May 2022 08:36:49 +0200 [thread overview]
Message-ID: <6a44aa70-e778-a115-6e4a-1336fef6c951@kaod.org> (raw)
In-Reply-To: <3C811C58-AF56-412B-B567-1218076B7584@fb.com>
>>> Have you considered extending the emulation to include a AST1030 SoC
>>> in a larger machine ?
>>>
>>> The AST1030 SoC is merged and I think that QEMU could run a cortex-m4
>>> CPU and a A7 CPU. A + R CPUs is supported (Xilinx boards).
>>>
>>
>> As a matter of fact yes! I tested booting our OpenBIC Zephyr kernel last week with the 1030, that worked. I also used the experimental i2c multi-master patches from Klaus to make a i2c-netdev device that connects two separate QEMU instances through a socket and sends their i2c messages back and forth. I was able to test a basic MCTP transaction.
>>
>> I’m hoping to help however possible with merging Klaus’s changes, and then propose the i2c-netdev thing too.
>
> Oh wait a minute: You mean I could include both SoC’s in one machine?
Yes. We would need to extend the Aspeed machines to instantiate
2 different SoCs (or more). This is something quite interesting
to design.
> Oh that’s a good idea actually. Maybe I’ll look into that as an alternative to the socket thing. Still, it might be something useful to submit anyways.
Yes. Please do.
Thanks,
C.
next prev parent reply other threads:[~2022-05-06 6:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 22:59 [PATCH v2 0/1] hw/arm/aspeed: Add fby35 machine type Peter Delevoryas
2022-05-03 22:59 ` [PATCH v2 1/1] " Peter Delevoryas
2022-05-04 7:39 ` Cédric Le Goater
2022-05-04 16:34 ` Peter Delevoryas
2022-05-04 19:07 ` Peter Delevoryas
2022-05-06 6:36 ` Cédric Le Goater [this message]
2022-05-06 6:30 ` Cédric Le Goater
2022-05-06 6:56 ` Klaus Jensen
2022-05-06 17:16 ` Peter Delevoryas
2022-05-25 8:40 ` Cédric Le Goater
2022-05-25 15:27 ` Peter Delevoryas
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=6a44aa70-e778-a115-6e4a-1336fef6c951@kaod.org \
--to=clg@kaod.org \
--cc=patrick@stwcx.xyz \
--cc=pdel@fb.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 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.