From: Stephen Hemminger <stephen@networkplumber.org>
To: Jim Thompson <jim@netgate.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] GPL/LGPL .vs BSD license
Date: Sun, 27 Sep 2015 22:31:54 -0700 [thread overview]
Message-ID: <20150927223154.33f84045@urahara> (raw)
In-Reply-To: <E24C36BE-C344-467A-B999-679B264CECB8@netgate.com>
On Sun, 27 Sep 2015 20:44:41 -0500
Jim Thompson <jim@netgate.com> wrote:
> The following files have LGPL or GPL licenses. I can see the libretto_eal and the four files that are part of DTS being GPL, but there others seem like a mistake.
> Especially the docs, and the presence of the LICENSE.LGPL file.
>
> Is it possible to clean these up and make them BSD licensed?
>
> Jim
No. KNI, Xen, and IGB UIO must be GPL licensed since they are kernel drivers.
The other stuff header files should be dual licensed.
> # QEMU Guest Agent Client
> ./dts/dep/QMP/qemu-ga-client
> ./dts/dep/QMP/qmp.py
>
> Came from Scapy
> ./dts/dep/lldp.py
>
> Texttable Framework (LGPL)
> ./dts/framework/texttable.py
>
> These are part of DPDK proper:
> ./dpdk/LICENSE.LGPL
> ./dpdk/app/test/test_mempool.c
> ./dpdk/doc/guides/freebsd_gsg/build_dpdk.rst
> ./dpdk/doc/guides/linux_gsg/build_dpdk.rst
> ./dpdk/doc/guides/nics/mlx4.rst
> ./dpdk/doc/guides/sample_app_ug/img/l2_fwd_virtenv_benchmark_setup.png
> ./dpdk/lib/librte_eal/bsdapp/eal/include/exec-env/rte_dom0_common.h
> ./dpdk/lib/librte_eal/common/include/rte_pci_dev_feature_defs.h
> ./dpdk/lib/librte_eal/common/include/rte_pci_dev_features.h
> ./dpdk/lib/librte_eal/common/include/rte_pci_dev_ids.h
> ./dpdk/lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h
> ./dpdk/lib/librte_eal/linuxapp/eal/include/exec-env/rte_kni_common.h
> ./dpdk/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
> ./dpdk/lib/librte_eal/linuxapp/kni/ethtool/igb/COPYING
> ./dpdk/lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c
> ./dpdk/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat_ethtool.c
> ./dpdk/lib/librte_eal/linuxapp/kni/ethtool/ixgbe/COPYING
> ./dpdk/lib/librte_eal/linuxapp/kni/ethtool/ixgbe/ixgbe_main.c
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_dev.h
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_ethtool.c
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_fifo.h
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_misc.c
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_net.c
> ./dpdk/lib/librte_eal/linuxapp/kni/kni_vhost.c
> ./dpdk/lib/librte_eal/linuxapp/xen_dom0/dom0_mm_dev.h
> ./dpdk/lib/librte_eal/linuxapp/xen_dom0/dom0_mm_misc.c
> ./dpdk/lib/librte_vhost/eventfd_link/eventfd_link.c
> ./dpdk/lib/librte_vhost/eventfd_link/eventfd_link.h
> ./dpdk/pkg/dpdk.spec
>
prev parent reply other threads:[~2015-09-28 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 1:44 Jim Thompson
2015-09-28 5:31 ` Stephen Hemminger [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=20150927223154.33f84045@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=jim@netgate.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).