From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sponsorship for QEMU Developers...
Date: Sat, 05 Mar 2005 17:27:39 -0500 [thread overview]
Message-ID: <422A325B.1090301@win4lin.com> (raw)
In-Reply-To: <200503051413.36906.os2@videotron.ca>
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
next prev parent reply other threads:[~2005-03-05 22:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 20:11 [Qemu-devel] Sponsorship for QEMU Developers Leonardo E. Reiter
2005-03-04 22:08 ` Paul Brook
2005-03-04 22:10 ` Leonardo E. Reiter
2005-03-04 23:45 ` Joshua Kugler
2005-03-04 23:57 ` Magnus Damm
2005-03-05 19:13 ` Marc Collin
2005-03-05 22:27 ` Leonardo E. Reiter [this message]
2005-03-06 1:51 ` [Qemu-devel] " Robert Wittams
2005-03-06 2:48 ` Leonardo E. Reiter
2005-03-06 3:32 ` John R. Hogerhuis
2005-03-06 3:47 ` Jim C. Brown
2005-03-06 4:37 ` John R. Hogerhuis
2005-03-06 5:40 ` Leonardo E. Reiter
2005-03-06 9:01 ` John R. Hogerhuis
2005-03-06 11:42 ` Robert Wittams
2005-03-06 9:45 ` Jonas Maebe
2005-03-06 10:28 ` Jonas Maebe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422A325B.1090301@win4lin.com \
--to=lreiter@win4lin.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).