From: Michael Qiu <fallwind@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to add a new machine support in qemu?
Date: Fri, 6 Nov 2009 16:18:31 +0800 [thread overview]
Message-ID: <f74f98340911060018g61807a2cmf9261998ce8dfb19@mail.gmail.com> (raw)
In-Reply-To: <ef2f888d0911052048s2146d94ci1d914e950f3678fc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
Thanks for your reply. I'm reading hw/mips_r4k.c. But I found I should dive
into the source code.
I'm looking for some big picture level document for add a new machine using
a supported core.
It seems qemu consists 3 parts of code
1. The core dynamic translate engineer to support several archs, just like
mips, arm, ppc....
2. The peripheral emulation pool.
3. The platform relative code, just like hw/mips_jazz.c ..., it just connect
the arch and the peripherals according to the real board.
I think my work should be the 2 and 3. And I'd like to find some documents
for them.
[-- Attachment #2: Type: text/html, Size: 620 bytes --]
next prev parent reply other threads:[~2009-11-06 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 3:46 [Qemu-devel] How to add a new machine support in qemu? Michael Qiu
2009-11-06 4:43 ` Scott Tsai
2009-11-06 4:48 ` Scott Tsai
2009-11-06 8:18 ` Michael Qiu [this message]
2009-11-06 11:03 ` Stefan Weil
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=f74f98340911060018g61807a2cmf9261998ce8dfb19@mail.gmail.com \
--to=fallwind@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).