From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D7i44-0002Og-4A for qemu-devel@nongnu.org; Sat, 05 Mar 2005 17:48:04 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D7i40-0002Mc-Nt for qemu-devel@nongnu.org; Sat, 05 Mar 2005 17:48:01 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D7i40-0002MK-L2 for qemu-devel@nongnu.org; Sat, 05 Mar 2005 17:48:00 -0500 Received: from [216.58.162.138] (helo=netraverse.com) by monty-python.gnu.org with esmtp (SSLv3:DES-CBC3-SHA:168) (Exim 4.34) id 1D7hkS-0005CL-KU for qemu-devel@nongnu.org; Sat, 05 Mar 2005 17:27:48 -0500 Received: from [69.165.224.96] (account lreiter HELO [10.1.0.1]) by netraverse.com (CommuniGate Pro SMTP 4.0.5) with ESMTP-TLS id 4678617 for qemu-devel@nongnu.org; Sat, 05 Mar 2005 14:47:11 -0700 Message-ID: <422A325B.1090301@win4lin.com> Date: Sat, 05 Mar 2005 17:27:39 -0500 From: "Leonardo E. Reiter" MIME-Version: 1.0 Subject: Re: [Qemu-devel] Sponsorship for QEMU Developers... References: <4228C0D9.8000601@win4lin.com> <200503051413.36906.os2@videotron.ca> In-Reply-To: <200503051413.36906.os2@videotron.ca> 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 Marc, here is an easy link to use: ftp://ftp.win4lin.com/pub/oss/ oss stands for Open Source Software of course. the qemu tarball is a CVS head snapshot from the 2/20/05; mergepro.patch gets applied to it to add our 3rd party stuff. Basically what we do is enable loading a dynamic shared object as a "plugin", and export symbols back and forth as needed by supplying pointers to them both in vl.c and in our plugin. We do not use any additional header files or anything like that in our closed source bits, since that would of course violate the GPL. We mainly did this so that we could "replace" the initialization of certain built-in peripherals in QEMU with our own proprietary versions that live in the plugin. To date, we replace the GUI ("display") and the IDE driver with our own home-grown versions. You will notice that all QEMU structures are passed in as void pointers back and forth, since we don't use any of the QEMU header files which define them. We instead get and set only the members we are interested in by address in our plugin. Note that this is fairly temporary. We are working on making all of QEMU a shared library object itself, and adding accessors (get/set) for each QEMU structure type that are exported from the shared library. This would encapsulate the GPL'd code in a much cleaner way, and would let us avoid having to calculate addresses of members in our closed-source code when getting or setting data from structures. Let me know if you have any additional questions. Best regards, Leo Reiter Marc Collin wrote: > HI > > where we can get source code of qemu you use in Win4Lin Pro? > > thanks -- Leonardo E. Reiter Vice President of Engineering Win4Lin, Inc. Virtual Computing from Desktop to Data Center Main: +1 512 339 7979 Fax: +1 512 532 6501 http://www.win4lin.com