From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LjFWt-0007IW-Ra for qemu-devel@nongnu.org; Mon, 16 Mar 2009 12:19:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LjFWo-0007DQ-5g for qemu-devel@nongnu.org; Mon, 16 Mar 2009 12:19:06 -0400 Received: from [199.232.76.173] (port=47328 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LjFWn-0007D6-RO for qemu-devel@nongnu.org; Mon, 16 Mar 2009 12:19:01 -0400 Received: from mail-bw0-f162.google.com ([209.85.218.162]:44353) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LjFWn-0007P8-Cg for qemu-devel@nongnu.org; Mon, 16 Mar 2009 12:19:01 -0400 Received: by bwz6 with SMTP id 6so1052311bwz.34 for ; Mon, 16 Mar 2009 09:18:59 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 16 Mar 2009 18:18:59 +0200 Message-ID: From: Alex Rozenman Content-Type: multipart/alternative; boundary=001636c598d6db892904653ece3c Subject: [Qemu-devel] a question about licensing 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 --001636c598d6db892904653ece3c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello, I would like to get a clarification about possibility to incorporate our proprietary code with QEMU in the following ways: 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). --001636c598d6db892904653ece3c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello,

I would like to get a clarification about possibility to inco= rporate our proprietary code with QEMU in the following ways:

Way 1.=
=3D=3D=3D=3D=3D
Let's assume that I changed QEMU allowing a poss= ibly 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). Ou= r customer wants to build an executable from following components:
1. Modified QEMU library.
2. Our proprietary library (e.g. mylib.a, myli= b.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 bec= ome GPL and the customer is intended to use it only internally. Is it possi= ble to keep my mylib.a proprietary and closed source ? Is it legal from QEM= U point of view ?

Way 2.
=3D=3D=3D=3D=3D
We will implement a kind of '-M" like option that will load a shar= eable library of a board (for example -M dynamic:my_board.so), find and call a fu= nction 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&= quot; and "write_physical_memory" etc.

--
Best regards,
Alex Rozenman (rozenman@gmail.com).

--001636c598d6db892904653ece3c--