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 18:21:52 +0100 [thread overview]
Message-ID: <20060607172152.GA3513@mail.shareable.org> (raw)
In-Reply-To: <200606071734.06090.paul@codesourcery.com>
Paul Brook wrote:
> > 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?
>
> As I mentioned before I have significant local patches implementing
> unreleased Arm features. The only way to avoid cross contamination
> between that and a third party qemu implementation two would be for
> me to stop contributing anything (or at minimum anything ARM
> related) back to qemu.
The idea is for someone else, working completely independently of you,
and without ever seeing those patches of yours, to provide the later
ARM support.
I know it doesn't feel good to think about someone else duplicating
the work you have done, but that's not a reason to not do it, if it's
the only legal solution to a useful feature.
So why "anything ARM related" and not "anything ARMv6 or later related"?
Isn't it sufficient for you to avoid contributing anything related to
the versions/features the restrictive license covers, so that you
could continue to contribute ARM related things for the older,
publically documented features?
That may feel uncomfortable, but it is no different than your present
situation. And for other people, it would provide a useful feature.
> Basing work on the gcc/binutils code doesn't help me either because I wrote
> most of that code in the first place :-)
Since the idea is for someone else do it, that doesn't matter.
I'm wondering why, if it were done, it would be a problem for you to
contribute in future in the areas which you contribute to now.
-- Jamie
next prev parent reply other threads:[~2006-06-07 17:22 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 [this message]
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=20060607172152.GA3513@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).