From: Paul Mackerras <paulus@samba.org>
To: akuster@mvista.com, Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: GPL inconsistency in arch/ppc/ocp/xlinx/
Date: Sun, 25 May 2003 22:01:57 +1000 [thread overview]
Message-ID: <16080.45237.64314.364407@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <20030524201213.GA8256@lst.de>
Christoph Hellwig writes:
> you seem to have added the the directory in the topic to the LinuxPPC
> trees. Unfortunately they have a license consitency that basically
> makes them illegal to distribute, they claim to be under GPL but have
> the following notice:
>
> * Xilinx products are not intended for use in life support appliances,
> * devices, or systems. Use in such applications are expressly prohibited.
>
> Could you please contact Xilinc to clarify the license and/or remove
> those files from the tree? Thanks.
It would depend on whether those files are a "Xilinx product" or not.
I would take that statement as normally applying to the hardware they
produce (i.e. their FPGAs). I agree it needs to be clarified though.
I also notice that their statement in upper case just above that says
that you are responsible for obtaining any rights you may require for
your implementation, which could be seen as conflicting with the
patent grant section of the GPL.
Armin, could you ask Xilinx if they would mind clarifying these two
points? Perhaps they could add a statement saying that if any of
those terms conflict with the GPL then the GPL is to prevail - although,
the best thing would be to remove the extra paragraphs, since the GPL
covers the disclaimer of warranty, patent concerns, etc. already.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-25 12:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 20:12 GPL inconsistency in arch/ppc/ocp/xlinx/ Christoph Hellwig
2003-05-25 12:01 ` Paul Mackerras [this message]
2003-06-12 20:32 ` Christoph Hellwig
2003-06-12 20:44 ` Larry McVoy
2003-06-13 7:58 ` Giuliano Pochini
2003-06-15 17:39 ` Christoph Hellwig
2003-06-12 20:45 ` Matt Porter
2003-06-15 17:41 ` Christoph Hellwig
2003-06-16 0:07 ` Tom Rini
2003-06-12 20:55 ` Tom Rini
2003-06-15 17:47 ` Christoph Hellwig
2003-06-16 0:04 ` Tom Rini
2003-06-17 4:50 ` Peter Ryser
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=16080.45237.64314.364407@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=akuster@mvista.com \
--cc=hch@lst.de \
--cc=linuxppc-dev@lists.linuxppc.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).