From: Deepak Saxena <dsaxena@plexity.net>
To: Stefan Roese <sr@denx.de>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Integrating IXP4xx NPE support in kernel (with IXP4xx accesslibrary)
Date: Tue, 27 Dec 2005 15:12:28 -0800 [thread overview]
Message-ID: <20051227231228.GD31728@plexity.net> (raw)
In-Reply-To: <200512271045.24105.sr@denx.de>
On Dec 27 2005, at 10:45, Stefan Roese was caught saying:
>
> Understood. But a total rewrite of this code is unfortunately not an option,
> since it's just too much work (without a sponsor).
>
> > > 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?
>
> It's the complete ixp400 access library. The file available via the link above
> is called "IPL_ixp400AccessLibrary-2_0.zip" and the BSD version of it is
> called "BSD_ixp400AccessLibrary-2_0.zip". Only the license headers seem to be
> replaced. As I heard the 2.1 version should also be available in the BSD
> version in december, but I didn't get access to it until now.
If it ss already licensed as BSD minus the advertising clause, just make
your customer happy and integrate it as is into their kernel. There is
no point making a clean version of the library as it will never go
upstream.
~Deepak
--
Deepak Saxena - dsaxena@plexity.net - http://www.plexity.net
A starving child in Africa or you in front of your TV?
Where's the real tragedy?
-------------------------------------------------------------------
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
prev parent reply other threads:[~2005-12-27 23:12 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
2005-12-24 14:04 ` Deepak Saxena
[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
[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 [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=20051227231228.GD31728@plexity.net \
--to=dsaxena@plexity.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=sr@denx.de \
/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).