All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 24 Dec 2005 06:07:52 -0800	[thread overview]
Message-ID: <20051224140752.GC9840@plexity.net> (raw)
In-Reply-To: <200512211548.23070.sr@denx.de>

On Dec 21 2005, at 15:48, Stefan Roese was caught saying:
> Hi Lennert,
> 
> On Wednesday 21 December 2005 14:52, Lennert Buytenhek wrote:
> > On Wed, Dec 21, 2005 at 01:00:34PM +0100, Stefan Roese wrote:
> > > The main question I have is, where should the IXP4xx access-library
> > > be located in the kernel directory structure?
> >
> > Maybe you can explain to the list readers what it is and what it does?
> 
> It's the library needed for the NPE (network processor engines) ethernet 
> driver to access the on chip NPE's (e.g. download microcode, communicate with 
> the NPE's etc.). Unfortunately a pretty big piece of software written to 
> support multiple OS's. :-(

As I mentioned in my earlier reply, we don't want all those abstractions
in the kernel.

> 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?

~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

  parent reply	other threads:[~2005-12-24 14:07 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 [this message]
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
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=20051224140752.GC9840@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.