From: Jamie Lokier <jamie@shareable.org>
To: Paul Brook <paul@codesourcery.com>
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 17:18:23 +0100 [thread overview]
Message-ID: <20060607161823.GA31417@mail.shareable.org> (raw)
In-Reply-To: <200606071658.27892.paul@codesourcery.com>
Paul Brook wrote:
> > 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.
Of course, I'm sure you're right.
In the thread you cited earlier, Wolfgang Schildbach refers to "ARM
System Developer's Guide", by Sloss, Symes, and Wright, Elsevier 2004
as documentation that may be sufficient for Qemu ARMv6 support, and
which is not covered by the license.
If ARMv6 support were developed by someone else, using only that book,
and maybe looking at other code (GCC, Linux etc.), that would prove
that all the information used is from other sources not covered by the
license, wouldn't it?
The support might be missing a few features, if the other information
sources are incomplete, but even incomplete support that can be
deduced from those sources would be good enough for most purposes.
If that were done, you could prove that the resulting feature in Qemu
was written using sources not covered by the license.
So would you have any problem contributing to Qemu after ARMv6 support
was integrated, if the person who contributes ARMv6 support states
that they have never seen the ARM document and refers to the sources
they have used instead?
-- Jamie
next prev parent reply other threads:[~2006-06-07 16:18 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 [this message]
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=20060607161823.GA31417@mail.shareable.org \
--to=jamie@shareable.org \
--cc=paul@codesourcery.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).