From: Christopher Covington <cov@codeaurora.org>
To: Michael Matz <matz@suse.de>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
"Laurent Desnogues" <laurent.desnogues@gmail.com>,
"Patch Tracking" <patches@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alexander Graf" <agraf@suse.de>,
"Claudio Fontana" <claudio.fontana@linaro.org>,
"Dirk Mueller" <dmueller@suse.de>,
"Will Newton" <will.newton@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] disas: add libvixl to support A64 disassembly
Date: Thu, 06 Feb 2014 09:04:23 -0500 [thread overview]
Message-ID: <52F39667.2000505@codeaurora.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1402061453350.2204@wotan.suse.de>
On 02/06/2014 08:54 AM, Michael Matz wrote:
> Hi,
>
> On Thu, 6 Feb 2014, Peter Maydell wrote:
>
>> On 6 February 2014 13:45, Michael Matz <matz@suse.de> wrote:
>>> Hmm, why aren't we simply using the binutils disassembler? It's also
>>> (C) by ARM, so there shouldn't be any relicensing problems. And it
>>> does support AdvSIMD and system instructions.
>>
>> It is GPLv3 which is not compatible with GPLv2 which
>> QEMU requires. The contribution process for binutils
>> involves a copyright assignment which means the FSF
>> now have the copyright there, as I understand it.
>
> The FSF always grants back rights on the contribution to the contributor.
> ARM could simply double-license their original contribution of the
> disassembler.
Is dual licensing always possible given a grant-back? What if the contribution
is a derivative of a GPL-3.0 licensed work?
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-02-06 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 17:28 [Qemu-devel] [PATCH v3 0/5] disas: add libvixl to support A64 disassembly Peter Maydell
2014-02-05 17:28 ` [Qemu-devel] [PATCH v3 1/5] rules.mak: Support .cc as a C++ source file suffix Peter Maydell
2014-02-05 17:28 ` [Qemu-devel] [PATCH v3 2/5] rules.mak: Link with C++ if we have a C++ compiler Peter Maydell
2014-02-05 17:28 ` [Qemu-devel] [PATCH v3 3/5] disas: Add subset of libvixl sources for A64 disassembler Peter Maydell
2014-02-05 17:28 ` [Qemu-devel] [PATCH v3 4/5] disas/libvixl: Fix upstream libvixl compilation issues Peter Maydell
2014-02-05 17:28 ` [Qemu-devel] [PATCH v3 5/5] disas: Implement disassembly output for A64 Peter Maydell
2014-02-06 13:45 ` [Qemu-devel] [PATCH v3 0/5] disas: add libvixl to support A64 disassembly Michael Matz
2014-02-06 13:51 ` Peter Maydell
2014-02-06 13:54 ` Michael Matz
2014-02-06 14:04 ` Christopher Covington [this message]
2014-02-06 14:20 ` Michael Matz
2014-02-06 14:05 ` Peter Maydell
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=52F39667.2000505@codeaurora.org \
--to=cov@codeaurora.org \
--cc=agraf@suse.de \
--cc=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=claudio.fontana@linaro.org \
--cc=dmueller@suse.de \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=laurent.desnogues@gmail.com \
--cc=matz@suse.de \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=will.newton@linaro.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.