All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reeted <reeted@shiftmail.org>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: No more win2k virtio-net drivers in latest Fedora
Date: Sat, 31 Mar 2012 20:56:36 +0200	[thread overview]
Message-ID: <4F775364.60006@shiftmail.org> (raw)

Hello all,
I have noticed that the virtio-net drivers for win2k exist in the 3 
years' old:

http://sourceforge.net/projects/kvm/files/kvm-driver-disc/20081229/NETKVM-20081229.iso/download

but not in the newest:

http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-22.iso

Would you add such drivers back to fedora drivers release please,
or is that because you intentionally dropped support for win2k?

Are the 2008' drivers reasonably bug-free (i.e. no undetected data 
corruption)?

Thank you
R.

WARNING: multiple messages have this Message-ID (diff)
From: Reeted <reeted@shiftmail.org>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] No more win2k virtio-net drivers in latest Fedora
Date: Sat, 31 Mar 2012 20:56:36 +0200	[thread overview]
Message-ID: <4F775364.60006@shiftmail.org> (raw)

Hello all,
I have noticed that the virtio-net drivers for win2k exist in the 3 
years' old:

http://sourceforge.net/projects/kvm/files/kvm-driver-disc/20081229/NETKVM-20081229.iso/download

but not in the newest:

http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-22.iso

Would you add such drivers back to fedora drivers release please,
or is that because you intentionally dropped support for win2k?

Are the 2008' drivers reasonably bug-free (i.e. no undetected data 
corruption)?

Thank you
R.

             reply	other threads:[~2012-03-31 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31 18:56 Reeted [this message]
2012-03-31 18:56 ` [Qemu-devel] No more win2k virtio-net drivers in latest Fedora Reeted

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=4F775364.60006@shiftmail.org \
    --to=reeted@shiftmail.org \
    --cc=kvm@vger.kernel.org \
    --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 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.