From: Michael Eager <eager@eagerm.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to create new target port?
Date: Wed, 23 May 2012 12:04:36 -0700 [thread overview]
Message-ID: <4FBD34C4.6080000@eagerm.com> (raw)
In-Reply-To: <4FBD097B.2010708@weilnetz.de>
On 05/23/2012 08:59 AM, Stefan Weil wrote:
> Am 23.05.2012 16:37, schrieb Michael Eager:
>> On 05/22/2012 11:18 PM, 陳韋任 wrote:
>>>> I'm investigating adding a new target architecture
>>>> to QEMU. Are there documents, how-to's, or other
>>>> guidance on how to approach this? Or any advice?
>>>>
>>>> I noticed that there are a number of directories for
>>>> architectures like target-arm and target-mips. There
>>>> are also definitions under tcg for arm and mips. I
>>>> noticed that target-microblaze exists, but there is
>>>> no microblaze directory under tcg. What does this
>>>> mean?
>>>
>>> Depends on what you'd like to add, a guest or a host support. If you want to
>>> add a new guest, take target-xxx/* as an example. Otherwise, looks at tcg/xxx/*.
>>> The term "target" could be a little MISLEADING here. :)
>>
>> I'm interested in adding a new emulated architecture,
>> not a new host. So adding a new target-<arch> sounds
>> like the plan.
>
> Yes, that's the place for new target architectures.
>
> Which architecture are you thinking of? Maybe someone else
> is already working on it. http://wiki.qemu.org/Links has an
> incomplete list of links to unofficial versions of QEMU which
> support additional targets.
Thanks for the pointer. It's a proprietary architecture,
not one of those mentioned. I'll add it to the list as we
move forward with the project.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2012-05-23 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 2:03 [Qemu-devel] How to create new target port? Michael Eager
2012-05-23 6:18 ` 陳韋任
2012-05-23 14:37 ` Michael Eager
2012-05-23 15:59 ` Stefan Weil
2012-05-23 19:04 ` Michael Eager [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=4FBD34C4.6080000@eagerm.com \
--to=eager@eagerm.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.