netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Marc Singer <elf@buici.com>
Cc: netdev@vger.kernel.org, Deepak Saxena <dsaxena@plexity.net>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Integrating IXP4xx NPE support in kernel (with IXP4xx accesslibrary)
Date: Tue, 27 Dec 2005 10:54:39 +0100	[thread overview]
Message-ID: <200512271054.39629.sr@denx.de> (raw)
In-Reply-To: <20051224163653.GB18167@buici.com>

On Saturday 24 December 2005 17:36, Marc Singer wrote:
> > > It most likely is the same code. Currently it's version 2.0. This
> > > version is available under a special Intel license
> > > (http://www.intel.com/design/network/products/npfamily/ixp425swr1.htm)
> > > and under the BSD license (when you bug your Intel contact enough). The
> > > files seem to be the same, only the header with the license is
> > > exchanged.
> >
> > I'll take a look a this some more, but is it just the HAL or the whole
> > stack that's open?
>
> I chatted with Lennert about this and was, well, amazed.  In reading
> what I see on the web site, it looks to me that the library is still
> heavily guarded. They're publishing a GPL'd 'driver' that links with
> the library.

Yes, that's the ethernet driver using this access lib to communicate with the 
NPE's. This driver is published under the GPL.

> The click-through license establishes the same ol' terms.  "You can
> only distribute this software with a hardware product."
>
> Please show me where this new BSD license appears.

As far as I know, you can't find it on the Intel web site. As mentioned 
earlier, we (or our customer) had a lot of discussions with our Intel 
contacts, about getting a version of this access lib under a license allowing 
us to include it in GPL projects (U-Boot and Linux kernel). Finally we got 
access to this BSD version of this library, which seems to exist for quite 
some time. Please don't ask me why this version is not published officially 
by Intel.
 
Best regards,
Stefan

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

  reply	other threads:[~2005-12-27  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051220230806.619131000@localhost.localdomain>
     [not found] ` <200512211300.38163.sr@denx.de>
2005-12-21 13:52   ` Integrating IXP4xx NPE support in kernel (with IXP4xx accesslibrary) Lennert Buytenhek
     [not found]     ` <200512211548.23070.sr@denx.de>
2005-12-21 23:37       ` Lennert Buytenhek
2005-12-24 14:07       ` Deepak Saxena
2005-12-24 16:36         ` Marc Singer
2005-12-27  9:54           ` Stefan Roese [this message]
     [not found]             ` <1135691390.5818.99.camel@localhost.localdomain>
2005-12-27 23:06               ` Deepak Saxena
     [not found]               ` <m3fyoek4yl.fsf@defiant.localdomain>
2005-12-27 23:11                 ` Deepak Saxena
2005-12-27  9:45         ` Stefan Roese
2005-12-27 23:12           ` Deepak Saxena
2005-12-24 14:04     ` Deepak Saxena

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=200512271054.39629.sr@denx.de \
    --to=sr@denx.de \
    --cc=dsaxena@plexity.net \
    --cc=elf@buici.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=netdev@vger.kernel.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).