From: Peter Ryser <Peter.Ryser@xilinx.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Christoph Hellwig <hch@lst.de>,
Peter Ryser <Peter.Ryser@xilinx.com>,
akuster@mvista.com, linuxppc-embedded@lists.linuxppc.org,
Scott Anderson <sanders@mvista.com>,
Paul Mackerras <paulus@samba.org>,
Rafael Aguirre-Sacasa <Rafael.Aguirre-Sacasa@xilinx.com>
Subject: Re: GPL inconsistency in arch/ppc/ocp/xlinx/
Date: Mon, 16 Jun 2003 21:50:19 -0700 [thread overview]
Message-ID: <3EEE9E0B.87DE9E6F@xilinx.com> (raw)
In-Reply-To: 20030612205523.GI828@ip68-0-152-218.tc.ph.cox.net
I'm working with our legal departement on straightening the licensing issues
out. Our intention is to distribute the source code under GPL. Most likely, we
will remove
* Xilinx products are not intended for use in life support
* appliances, devices, or systems. Use in such applications are
* expressly prohibited.
without replacement.
- Peter
Tom Rini wrote:
> 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:
> > >
> > > 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.
>
> I think you should ask someone responsible first. And on the correct
> mailing list as well. Armin is not responsible for this code, Scott
> Anderson is. Armin just put it into the linuxppc-2.5 tree. Second,
> Peter Ryser (who handles the Xilinx side of things) is on the
> linuxppc-embedded list, where most of the 4xx people are. Finally,
> Peter knows about this, and last I knew was talking to their legal
> department. Peter, any news on this?
>
> --
> Tom Rini
> http://gate.crashing.org/~trini/
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-06-17 4:50 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
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 [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=3EEE9E0B.87DE9E6F@xilinx.com \
--to=peter.ryser@xilinx.com \
--cc=Rafael.Aguirre-Sacasa@xilinx.com \
--cc=akuster@mvista.com \
--cc=hch@lst.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=sanders@mvista.com \
--cc=trini@kernel.crashing.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).