All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Wolfe <brianw@terrabox.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: RE: GPL Win PV driver issues
Date: Tue, 01 Jan 2008 13:06:15 -0600	[thread overview]
Message-ID: <1199214375.4866.10.camel@localhost.localdomain> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131A4FB@trantor>

I wish I could help out a bit by compiling for nt2k pro but
unfortunately MS wants me to buy their developers subscription for $1k+
USD. 8-( I can't afford that kind of cash. *sigh*

If anyone can front me the necessary installables for compiling the
windows PV drivers I'm willing to have a go at helping out. :) 


On Sat, 2007-12-15 at 09:17 +1100, James Harper wrote:
> > 
> > I've been thinking about this. Isn't it possible to allow both QEMU
> and
> > PV devices to exist, and create a combined HW/PV driver? I.e., a
> driver
> > for both the emulated device under Windows (as a later version than
> the
> > one shipped in Windows). Then, if really running under Xen, the driver
> > instructs dom0 to optionally terminate the QEMU server side and use
> the
> > PV approach for communication.
> > 
> > As the emulated devices are well understood (and there's QEMU's
> source),
> > would this be hard to do?
> > 
> 
> The way I've implemented the driver for the Xen PCI device is that it
> becomes a bus driver and enumerates the things under 'devices' in
> xenstore (eg vbd, vif, console) and then drivers attach to those.
> 
> For your idea to work, a single driver would need to attach to both the
> emulated PCI disk/network adapter, and the Xen PV device. I don't think
> this is possibly under the windows driver model.
> 
> But I've only been writing windows drivers for a few months now, so
> there's probably a lot of stuff I don't know :)
> 
> James
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2008-01-01 19:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 21:05 GPL Win PV driver issues Andy Grover
2007-12-14  0:13 ` James Harper
2007-12-14 19:21   ` Steve Ofsthun
2007-12-14 19:36     ` Luciano Rocha
2007-12-14 19:42       ` Stefan de Konink
2007-12-14 20:16         ` Luciano Rocha
2007-12-14 22:19           ` James Harper
2007-12-14 20:40       ` Daniel P. Berrange
2007-12-14 21:51         ` Steve Ofsthun
2007-12-15  4:09           ` Mark Williamson
2007-12-15 16:50             ` Daniel P. Berrange
2007-12-15 16:52           ` Daniel P. Berrange
2007-12-16  5:59             ` James Harper
2007-12-14 22:21         ` James Harper
2007-12-14 22:37           ` Andy Grover
2007-12-14 22:53             ` James Harper
2007-12-14 22:17       ` James Harper
2008-01-01 19:06         ` Brian Wolfe [this message]
2008-01-02  2:45           ` James Harper
2008-01-02  3:32             ` Brian Wolfe
2008-01-02  4:20               ` James Harper
2008-01-02  7:24                 ` Brian Wolfe
2008-01-02  8:44                   ` James Harper
2008-01-20 10:19                     ` Stephan Seitz
2008-01-20 10:29                       ` James Harper

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=1199214375.4866.10.camel@localhost.localdomain \
    --to=brianw@terrabox.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.