From: Deepak Saxena <dsaxena@plexity.net>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: netdev@vger.kernel.org, hadi@cyberus.ca,
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:11:07 -0800 [thread overview]
Message-ID: <20051227231107.GC31728@plexity.net> (raw)
In-Reply-To: <m3fyoek4yl.fsf@defiant.localdomain>
On Dec 27 2005, at 15:08, Krzysztof Halasa was caught saying:
> jamal <hadi@cyberus.ca> writes:
>
> > No experience with the 4xx but some with the other intel NPs.
> > Is the driver a "dual stack" approach that Intel typically
> > has?
>
> No, the Ethernet driver is Linux-only and uses the access library.
> Both are crap BTW, the library is much worse.
>
> Actually I think the whole library needs to be rewritten from (almost)
> scratch (resulting in 5% or less code), and the Ethernet driver wouldn't
> be a problem then. The BSD-licensed version would of course help.
>
> > Intel should be able to fund you to rewrite it - convincing them
> > they are going to sell more chips this way seems to be not too
> > hard, no?
>
> Any Intel contacts interested? I could possibly earn some money as
> well :-)
Good luck. I've been working closely with Intel on the kernel side of the
IXP for 3 years now and the only business person in that division that
understood the benefits of the going to GPL and how the Linux world works
is no longer there. From their point of view, it is simpler to have a single
codebase shared among VxWorks, WinCE, Linux, and QNX (?) than to have a
separate Linux version.
~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
next prev parent reply other threads:[~2005-12-27 23:11 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 [this message]
2005-12-27 9:45 ` Stefan Roese
2005-12-27 23:12 ` 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=20051227231107.GC31728@plexity.net \
--to=dsaxena@plexity.net \
--cc=hadi@cyberus.ca \
--cc=khc@pm.waw.pl \
--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).