From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] I want to add the ARMv6 instructions, who can give some advices?
Date: Wed, 7 Jun 2006 15:46:54 +0100 [thread overview]
Message-ID: <20060607144654.GA12715@mail.shareable.org> (raw)
In-Reply-To: <200606071435.52969.paul@codesourcery.com>
Paul Brook wrote:
> On Wednesday 07 June 2006 08:11, wang lianwei wrote:
> > I want to add the ARMv6 instructions support to the QEMU, and now I am
> > analysing the QEMU architecture. I think maybe someone has done it
> > or doing it now.
> >
> > Can you give me some guide about this work or give your suggestions?
>
> I have already implemented armv6 and armv7 support in qemu, but am unable to
> distribute it for legal reasons.
>
> See the previous thread on this topic:
> http://lists.gnu.org/archive/html/qemu-devel/2006-03/msg00199.html
>
> If you want armv6 support in qemu your best bet is to contact ARM
> and persuade them to lift this restriction.
There were three suggestions in that thread, and persuading ARM Ltd to
lift the restriction was one of them.
The other two suggestions were:
1. For someone who is not bound by an ARM documentation license
to do it, for example by working out the instruction set from
reading Binutils, GCC and Linux code, and from reading books
like the "ARM System Developer's Guide", by Sloss, Symes, and
Wright, Elsevier 2004.
The objection was raised that although that would be possible,
it would prevent some people (who are bound by an ARM license)
from contributing to the new Qemu.
I think that would not be a problem if the ARMv6 support were in
the form of a contributed patch, which those people could avoid
looking at.
2. To add an explanation of why ARMv6 isn't supported to Qemu's FAQ.
Anyone in a position to add to the FAQ?
-- Jamie
next prev parent reply other threads:[~2006-06-07 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 7:11 [Qemu-devel] I want to add the ARMv6 instructions, who can give some advices? wang lianwei
2006-06-07 13:35 ` Paul Brook
2006-06-07 14:38 ` John R.
2006-06-07 14:46 ` Paul Brook
2006-06-07 14:53 ` Jamie Lokier
2006-06-07 15:07 ` Paul Brook
2006-06-07 15:48 ` Jamie Lokier
2006-06-07 15:58 ` Paul Brook
2006-06-07 16:18 ` Jamie Lokier
2006-06-07 16:34 ` Paul Brook
2006-06-07 17:21 ` Jamie Lokier
2006-06-07 17:25 ` Paul Brook
2006-06-07 17:42 ` John R.
2006-06-07 18:36 ` Jamie Lokier
2006-06-07 14:46 ` Jamie Lokier [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-07 14:58 Laurent DESNOGUES
2006-06-07 16:34 Laurent DESNOGUES
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=20060607144654.GA12715@mail.shareable.org \
--to=jamie@shareable.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 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).