From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I1V53-0006bv-A3 for qemu-devel@nongnu.org; Thu, 21 Jun 2007 18:24:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I1V51-0006bd-Qm for qemu-devel@nongnu.org; Thu, 21 Jun 2007 18:24:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I1V51-0006ba-Ju for qemu-devel@nongnu.org; Thu, 21 Jun 2007 18:24:43 -0400 Received: from cpe-24-31-250-242.kc.res.rr.com ([24.31.250.242] helo=hachi.dashjr.org) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I1V51-0006QW-9i for qemu-devel@nongnu.org; Thu, 21 Jun 2007 18:24:43 -0400 Received: from [192.168.29.4] (adsl-76-194-177-181.dsl.ksc2mo.sbcglobal.net [76.194.177.181]) (Authenticated sender: luke-jr) by hachi.dashjr.org (Postfix) with ESMTP id B4EAB960031 for ; Thu, 21 Jun 2007 22:24:34 +0000 (UTC) From: Luke -Jr Subject: Re: [Qemu-devel] QEMU License and proprietary hardware Date: Thu, 21 Jun 2007 17:24:25 -0500 References: <7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com> In-Reply-To: <7d3e40d50706210428g11396d53y73fc12d326d71a59@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706211724.25832.luke@dashjr.org> 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 On Thursday 21 June 2007 06:28, Armbrost Failsafe wrote: > 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? Yep, that's the purpose of the GPL. It'll probably get a lot of people promoting it if you do a public release, too...