From: Larry McVoy <lm@bitmover.com>
To: Christoph Hellwig <hch@lst.de>
Cc: akuster@mvista.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: GPL inconsistency in arch/ppc/ocp/xlinx/
Date: Thu, 12 Jun 2003 13:44:44 -0700 [thread overview]
Message-ID: <20030612204444.GA19453@work.bitmover.com> (raw)
In-Reply-To: <20030612203205.GA23017@lst.de>
On Thu, Jun 12, 2003 at 10:32:05PM +0200, Christoph Hellwig wrote:
>
> On Sat, May 24, 2003 at 10:12:13PM +0200, Christoph Hellwig wrote:
> > Hi Armin,
> >
> > 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.
>
> As there hasn't been any answer yet I think these files should be
> remove to ensure the linuxppc tree is legally distributable.
Note: I don't care one way or the other how or if this is resolved. I'm
just making an observation.
You might want to be careful about advertising why you want these files
removed because the Xilinx clause is just covering their butt. If someone
uses Linux in some life support system and someone dies, the fact that
the community removed these files because of that clause could be construed
as a statement that Linux was suitable for life support systems. It gives
the lawyers ammo.
Personally, I wouldn't get that excited about that clause, I think that
enforcing the GPL to that extent on principle is likely to backfire. But
that's my opinion and worth what you paid for it.
Neither I nor BitMover have any sort of relationship with Xilinx, this is
just my opinion.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-12 20:44 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
2003-06-12 20:32 ` Christoph Hellwig
2003-06-12 20:44 ` Larry McVoy [this message]
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=20030612204444.GA19453@work.bitmover.com \
--to=lm@bitmover.com \
--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).