From: Paul Brook <paul@codesourcery.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: 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 16:58:27 +0100 [thread overview]
Message-ID: <200606071658.27892.paul@codesourcery.com> (raw)
In-Reply-To: <20060607154853.GA29923@mail.shareable.org>
> > Specifically clause 2(i):
> > "No right is granted to [...] use the ARM Architecture Reference
> > Manual for the purposes of developing or having developed
> > microprocessor cores or models thereof which are compatible in whole
> vvvv
> > or part with either or both the instructions or programmer's models
> ^^^^
> > described in this ARM Architecture Reference Manual"
>
> Qemu is already compatible "in part" with the the instructions and
> models described in the manual, isn't it?
>
> So by the language of clause 2(i), aren't you _already_ prohibited from
> working on Qemu's ARM code?
All the information used to implement the current qemu Arm support is
available from other sources not covered by this licence. I'm confident I
could prove this if necessary.
Paul
next prev parent reply other threads:[~2006-06-07 15:58 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 [this message]
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
-- 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=200606071658.27892.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=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 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.