From: Yusuf Kaya <ysf.kya34@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Question] Interest in IFC modeling or missing parts for T1042 SoC?
Date: Wed, 3 Sep 2025 12:28:32 +0300 [thread overview]
Message-ID: <CAHd9c1rBcf5SZFYQ2z0E86pmo9NPDTC7ScLMLzfg2yETz1whpQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
Hi QEMU developers,
I have experience with the T1042 SoC and I’d like to contribute to the QEMU
community. I couldn’t find any existing model of the IFC (Integrated Flash
Controller). At first, I assumed it might be missing, but later I thought
it could have been intentionally left out. However, I’m not sure.
So I’d like to ask: is there any interest or need in the community for
modeling IFC? Perhaps since QEMU mostly targets systems at the OS level,
early hardware bring-up stages (like IFC behavior or RCW loading) were
intentionally not included.
Also, if there’s anything else that you think is currently missing or
incomplete specifically regarding the T1042 SoC, I’d be happy to hear your
thoughts.
Thank you,
Yusuf Kaya.
[-- Attachment #2: Type: text/html, Size: 800 bytes --]
reply other threads:[~2025-09-03 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHd9c1rBcf5SZFYQ2z0E86pmo9NPDTC7ScLMLzfg2yETz1whpQ@mail.gmail.com \
--to=ysf.kya34@gmail.com \
--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).