qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH [1/2] Patches to support Juniper Olives - eepro100 multicast
Date: Mon, 27 Oct 2008 02:16:20 +0200	[thread overview]
Message-ID: <fb249edb0810261716h5948b478jbb77ab9a5a5cb65e@mail.gmail.com> (raw)
In-Reply-To: <d81b6b610810161446j62c8f4efk587872cf196b74f2@mail.gmail.com>

2008/10/16 Brandon Bennett <bennetb@gmail.com>:
> These patches are what I found was needed/wanted to support a "Juniper
> Olive".   Juniper routers run on off the shelf x86 archecture as a
> result you can load JunOS (the software that runs on Juniper routers)
> onto any standard PC and run it as an Olive.   Olive is the state of a
> router without a PFE (the forwarding plane of a juniper router).  The
> olive allows you to do most Juniper routing allowing you to study for
> certifications, test out network changes, or test new features.
>
> More information here:  http://juniper.cluepon.net/index.php/Olive
>
> The first patch is to update eepro100.c to the latest version found
> from Stefan Weil's ar7-firmware qemu trunk.   This patch is essential
> as it fixes multicast with the eepr100 supported nics.   Olive routers
> only support this nic so it is essential.
>
> This patch is line for line from Weil's respository with no changes.
> I hope this is alright to support others work.

I think so.

Note that the patch changes the license for eepro100.c to GPL3+.  I'm
no expert on this but I believe doing this would prohibit people from
distributing qemu packages.

Cheers

      reply	other threads:[~2008-10-27  0:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 21:46 [Qemu-devel] PATCH [1/2] Patches to support Juniper Olives - eepro100 multicast Brandon Bennett
2008-10-27  0:16 ` andrzej zaborowski [this message]

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=fb249edb0810261716h5948b478jbb77ab9a5a5cb65e@mail.gmail.com \
    --to=balrogg@gmail.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).