xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: <djmagee@mageenet.net>
To: Roderick Colenbrander <thunderbird2k@gmail.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
	xen-devel@lists.xensource.com, lta@akr.fm
Subject: Re: GPLPV and pci passthrough
Date: Tue, 31 Jan 2012 12:20:20 -0500	[thread overview]
Message-ID: <EECC125FCE18E740AF561189E12602851451D4@mnetexch2.adamapps.host> (raw)
In-Reply-To: <CAEc3jaArdDQL5+k-jdgW0idGpoUpq4CXzfg4QafJ660B8OjiRg@mail.gmail.com>

> On Mon, Jan 30, 2012 at 7:22 PM,  <djmagee@mageenet.net> wrote:
> >> I have had weird network problems as well using the 308 drivers.
For
> >> me the 356 drivers from the hg repository do work fine, so
something
> >> between 308 and 356 fixed some network bugs. Perhaps put a test
> build
> >> on the website for him to try?
> >>
> >
> > I already have the Windows DDK installed on a couple of machines,
but
> > the link to the hg repo at
> > http://wiki.xen.org/wiki/Xen_Windows_GplPv/Building seems to be
> broken.
> > Where's the current repo housed?
> 
> You can find it here:
> http://xenbits.xen.org/ext/win-pvdrivers/
> 
> Look at the README file of the source tree for additional build
> instructions.
> 
> Roderick

Thanks, that was easy enough.

I built the latest code available from the hg repo and I have the same
symptoms.  I'll dig around and see if I can find a good place to dump
some debug output and track down the problem.

Doug

  reply	other threads:[~2012-01-31 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 18:03 GPLPV and pci passthrough djmagee
2012-01-25 19:19 ` Pavel Matěja
2012-01-26  0:23 ` James Harper
2012-01-27 19:02   ` djmagee
2012-01-28 14:50     ` djmagee
2012-01-29  2:36       ` James Harper
2012-01-29 17:14         ` Roderick Colenbrander
2012-01-30 19:22           ` djmagee
2012-01-30 19:42             ` Roderick Colenbrander
2012-01-31 17:20               ` djmagee [this message]
2012-01-30 19:18         ` djmagee

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=EECC125FCE18E740AF561189E12602851451D4@mnetexch2.adamapps.host \
    --to=djmagee@mageenet.net \
    --cc=james.harper@bendigoit.com.au \
    --cc=lta@akr.fm \
    --cc=thunderbird2k@gmail.com \
    --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 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).