All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Ofsthun <sofsthun@virtualiron.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: Windows DDK and GPL
Date: Fri, 21 Sep 2007 14:52:32 -0400	[thread overview]
Message-ID: <46F412F0.9070303@virtualiron.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D012497DD@trantor>

James Harper wrote:
> During a recent discussion about the PV drivers for windows, someone
> made a comment about (I'm paraphrasing from memory here, I might be
> completely wrong) the Windows DDK being incompatible with the GPL, and
> thus even if you wanted to, any driver developed under the DDK could not
> be released under the GPL, or maybe even any other OSS license...
> 
> Can anyone point me to something which explicitly clarifies this? Or
> correct me if my interpretation is incorrect?

Here is a note from Bruce Vessey at Unisys from 11/01/2006.  Not so recent,
but the link to the EULA still works.

> It would be nice if somebody releases HVM paravirt drivers for Windows as
> open source, but I'm not holding my breath.  Why?  Because of the
> Microsoft DDK license.  There's no requirement that a Windows device
> driver developer use the Microsoft DDK, but in my experience most do.
> The typical methodology for a Windows driver developer is to take the
> sample code from the DDK as a starting point, and build the driver from
> there.  But the DDK has some interesting licensing restrictions that, to
> me, don't look compatible with open source.  The Microsoft DDK license is
> available at
> http://www.microsoft.com/whdc/devtools/ddk/ServerSP1DDKEULA.mspx
> Sections 3 & 4 look particularly problematic.
>
> Maybe somebody out there is developing (or has developed) Windows drivers
> without any encumbrances from the Windows DDK.  I think that's the only
> way we'll see open source Windows drivers.

Our Windows driver set is built using the Microsoft DDK.

Aside from any legal issues, our implementation of HVM live migrate is not
binary compatible with the current Xen 3.1 release.  This and other
compatibility issues (our 32 bit drivers use the same ring protocol as our
64 bit drivers) would prevent you from using our drivers directly.  This is
not a planned divergence, rather a consequence of getting something to work
reliably enough to ship at various points since 3.0.2.  Over time we have
been converging with generic XEN and at some future date I would expect
binary compatibility.

If a source distribution was not available, would a binary release be of
any use?

Hope this helps,
Steve
-- 
Steve Ofsthun - Virtual Iron Software, Inc.

  reply	other threads:[~2007-09-21 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21  2:09 Windows DDK and GPL James Harper
2007-09-21 18:52 ` Steve Ofsthun [this message]
2007-09-21 18:57   ` Vessey, Bruce A
2007-09-24  9:59   ` Pasi Kärkkäinen

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=46F412F0.9070303@virtualiron.com \
    --to=sofsthun@virtualiron.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.