From: Fabiano Rosas <farosas@suse.de>
To: Daoud LAMALMI <daoudlamalmi@pm.me>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: BALATON Zoltan <balaton@eik.bme.hu>,
Nicholas Piggin <npiggin@gmail.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Bernhard Beschow <shentey@gmail.com>
Subject: Re: MPC5553/MPC5554 Emulation (information request)
Date: Thu, 12 Dec 2024 10:49:32 -0300 [thread overview]
Message-ID: <87ed2df1ub.fsf@suse.de> (raw)
In-Reply-To: <kvndhk2oZokSDFW29-5pef8r1zmug70mTlHmrKT99LrvOaAflAeBV-vD6I6BAiAkHavpsN23lKJ6mN4Bd7UYFDe2tgbSegrXYVK6p-tR5F4=@pm.me>
Daoud LAMALMI via <qemu-devel@nongnu.org> writes:
> Goal
> ----
>
> I'd like to know if it is planned for QEMU to be able to emulate the MPC5553/MPC5554 microcontrollers.
>
> Technical details
> -----------------
>
> I know that the e200z6 processor can already be emulated. I don't know how much work is needed to emulate those microcontrollers fully based on the work that has already been done.
>
> Additional information
> ----------------------
>
> If it is not planned, I'll most likely start educating myself on this project to try and patch it in as it's a need that is quite important for me. I'll try not to waste your time and read as much as I can about your guidelines. Would you advise me against trying to do this? I'd like to know how hard you think this will be.
>
> DISCLAIMER : I am still very much a newbie in embedded systems, I'm only in the first year of my master's degree in embedded systems.
>
> Sent with Proton Mail secure email.
Adding some people to CC that might be able to help.
prev parent reply other threads:[~2024-12-12 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 5:45 MPC5553/MPC5554 Emulation (information request) Daoud LAMALMI via
2024-12-12 13:49 ` Fabiano Rosas [this message]
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=87ed2df1ub.fsf@suse.de \
--to=farosas@suse.de \
--cc=balaton@eik.bme.hu \
--cc=daoudlamalmi@pm.me \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.com \
/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.