From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LjZIC-0003BY-5P for qemu-devel@nongnu.org; Tue, 17 Mar 2009 09:25:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LjZI7-00037e-73 for qemu-devel@nongnu.org; Tue, 17 Mar 2009 09:25:15 -0400 Received: from [199.232.76.173] (port=44433 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LjZI7-00037Y-1q for qemu-devel@nongnu.org; Tue, 17 Mar 2009 09:25:11 -0400 Received: from qw-out-1920.google.com ([74.125.92.144]:47523) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LjZI6-0002st-P2 for qemu-devel@nongnu.org; Tue, 17 Mar 2009 09:25:10 -0400 Received: by qw-out-1920.google.com with SMTP id 5so7626qwf.4 for ; Tue, 17 Mar 2009 06:25:10 -0700 (PDT) Message-ID: <49BFA4B2.3000305@codemonkey.ws> Date: Tue, 17 Mar 2009 08:25:06 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] a question about licensing References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Alex Rozenman wrote: > Hello, > > I would like to get a clarification about possibility to incorporate > our proprietary code with QEMU in the following ways: Licensing questions should be directed to lawyers. I believe both scenarios go against the spirit of how QEMU is licensed though. There is no intention of allowing QEMU as a whole to be used in a closed product or for it to be able to load closed plugins. Regards, Anthony Liguori > Way 1. > ===== > Let's assume that I changed QEMU allowing a possibly to build it as > static/dynamic library (I needed to add a configuration option > replacing main by qemu_main and changing the main build target). Our > customer wants to build an executable from following components: > 1. Modified QEMU library. > 2. Our proprietary library (e.g. mylib.a, mylib.h) > 3. An open source "glue" file(s) containing calls to QEMU library as > well as to mylib.a > I understand that the executable will become GPL and the customer is > intended to use it only internally. Is it possible to keep my mylib.a > proprietary and closed source ? Is it legal from QEMU point of view ? > > Way 2. > ===== > We will implement a kind of '-M" like option that will load a > shareable library of a board (for example -M dynamic:my_board.so), > find and call a function in order to initialize the board and then run > normal QEMU main loop. The board code will define its own peripherals > and connect them to the CPU. It is obvious, that our proprietary code > shall not use any GPL peripherals and only call to GLPL functions like > "map_physical_memory" and "write_physical_memory" etc. > > -- > Best regards, > Alex Rozenman (rozenman@gmail.com ). >