From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I1KqO-0003QB-83 for qemu-devel@nongnu.org; Thu, 21 Jun 2007 07:28:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I1KqM-0003Pa-Fc for qemu-devel@nongnu.org; Thu, 21 Jun 2007 07:28:55 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I1KqM-0003PS-Ay for qemu-devel@nongnu.org; Thu, 21 Jun 2007 07:28:54 -0400 Received: from wx-out-0506.google.com ([66.249.82.229]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I1KqL-0002vt-Vr for qemu-devel@nongnu.org; Thu, 21 Jun 2007 07:28:54 -0400 Received: by wx-out-0506.google.com with SMTP id t15so480577wxc for ; Thu, 21 Jun 2007 04:28:53 -0700 (PDT) Message-ID: <7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com> Date: Thu, 21 Jun 2007 13:28:53 +0200 From: "Armbrost Failsafe" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_87199_11098368.1182425333315" Subject: [Qemu-devel] QEMU License and proprietary hardware Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_87199_11098368.1182425333315 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline We are looking into using QEMU as the base for a model of a custom system featuring some custom ASICs. But licensing issues are halting the process right now. Does anyone know what happens license-wise if we create a model of proprietary hardware using QEMU? Is that model automatically covered by the GPL and thus we have to give to anyone who asks about it? It is clear that if we keep it internal, it is OK. But anyone outside of our organization is to use it, shouldn't they automatically be entitled to receive the entire source of QEMU, including our models of proprietary devices? Even if these are developed from scratch without using any existing source code for devices? /armbrost ------=_Part_87199_11098368.1182425333315 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline We are looking into using QEMU as the base for a model of a custom system featuring some custom ASICs. But licensing issues are halting the process right now. Does anyone know what happens license-wise if we create a model of proprietary hardware using QEMU? Is that model automatically covered by the GPL and thus we have to give to anyone who asks about it? It is clear that if we keep it internal, it is OK. But anyone outside of our organization is to use it, shouldn't they automatically be entitled to receive the entire source of QEMU, including our models of proprietary devices? Even if these are developed from scratch without using any existing source code for devices?

/armbrost

------=_Part_87199_11098368.1182425333315--