Lennert Buytenhek <[EMAIL PROTECTED]> writes:
> I have a couple of ixp23xx boards at home, but I'm not sure whether I
> can give them away. I can give you remote access to them, though.
Hmm, may be interesting some day.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line
On Mon, May 07, 2007 at 09:18:00PM +0100, Michael-Luke Jones wrote:
> >Well, I'm told that (compatible) NPEs are present on other IXP CPUs.
> >Not sure about details.
>
> If, by a combined effort, we ever manage to create a generic NPE
> driver for the NPEs found in IXP42x/43x/46x/2000/23xx
On Mon, May 07, 2007 at 10:00:20PM +0200, Krzysztof Halasa wrote:
> > - the NPE can also be used as DMA engine and for crypto operations.
> > Both are not network related.
> > Additionally, the NPE is not only ixp4xx related, but is
> > also used in IXP23xx CPUs, so it could be placed in
>
On Mon, May 07, 2007 at 02:07:16AM +0200, Krzysztof Halasa wrote:
> + * Ethernet port config (0x00 is not present on IXP42X):
> + *
> + * logical port 0x000x100x20
> + * NPE 0 (NPE-A) 1 (NPE-B) 2 (NPE-C)
> + * physical PortId
On Mon, May 07, 2007 at 02:07:16AM +0200, Krzysztof Halasa wrote:
+ * Ethernet port config (0x00 is not present on IXP42X):
+ *
+ * logical port 0x000x100x20
+ * NPE 0 (NPE-A) 1 (NPE-B) 2 (NPE-C)
+ * physical PortId 2
On Mon, May 07, 2007 at 09:18:00PM +0100, Michael-Luke Jones wrote:
Well, I'm told that (compatible) NPEs are present on other IXP CPUs.
Not sure about details.
If, by a combined effort, we ever manage to create a generic NPE
driver for the NPEs found in IXP42x/43x/46x/2000/23xx then the
On Mon, May 07, 2007 at 10:00:20PM +0200, Krzysztof Halasa wrote:
- the NPE can also be used as DMA engine and for crypto operations.
Both are not network related.
Additionally, the NPE is not only ixp4xx related, but is
also used in IXP23xx CPUs, so it could be placed in
Lennert Buytenhek [EMAIL PROTECTED] writes:
I have a couple of ixp23xx boards at home, but I'm not sure whether I
can give them away. I can give you remote access to them, though.
Hmm, may be interesting some day.
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line unsubscribe
Christian Hohnstaedt <[EMAIL PROTECTED]> writes:
> - the NPE can also be used as DMA engine and for crypto operations.
> Both are not network related.
> Additionally, the NPE is not only ixp4xx related, but is
> also used in IXP23xx CPUs, so it could be placed in
> arch/arm/common or
Having thought about it a bit more, a layout similar to the one
proposed by you may make sense.
Michael-Luke Jones <[EMAIL PROTECTED]> writes:
> Despite their name, Network Processing Engines are independent
> coprocessors which are only coincidentally attached to MACs for
> ethernet / WAN
[Added Lennert Buytenhek to CC list]
Hey again,
Code placement:
Queue Manager & NPE code => arch/arm/mach-ixp4xx
WAN driver code => drivers/net/wan
Eth code => drivers/net/arm
Why would you want such placement?
Potential problems: header files would have to be moved to
include/asm-arm =
On Mon, May 07, 2007 at 07:12:49PM +0200, Krzysztof Halasa wrote:
> Michael-Luke Jones <[EMAIL PROTECTED]> writes:
>
> > Code placement:
> > Queue Manager & NPE code => arch/arm/mach-ixp4xx
> > WAN driver code => drivers/net/wan
> > Eth code => drivers/net/arm
>
> Why would you want such
Michael-Luke Jones <[EMAIL PROTECTED]> writes:
> Code placement:
> Queue Manager & NPE code => arch/arm/mach-ixp4xx
> WAN driver code => drivers/net/wan
> Eth code => drivers/net/arm
Why would you want such placement?
Potential problems: header files would have to be moved to
include/asm-arm =
On 7 May 2007, at 01:07, Krzysztof Halasa wrote:
Adds IXP4xx drivers for built-in CPU components:
- hardware queue manager
- NPE (network coprocessors),
- Ethernet ports,
- HSS (sync serial) ports (currently only non-channelized HDLC).
Both Ethernet and HSS drivers use queue manager and NPE
Michael-Luke Jones [EMAIL PROTECTED] writes:
Code placement:
Queue Manager NPE code = arch/arm/mach-ixp4xx
WAN driver code = drivers/net/wan
Eth code = drivers/net/arm
Why would you want such placement?
Potential problems: header files would have to be moved to
include/asm-arm = headers
On Mon, May 07, 2007 at 07:12:49PM +0200, Krzysztof Halasa wrote:
Michael-Luke Jones [EMAIL PROTECTED] writes:
Code placement:
Queue Manager NPE code = arch/arm/mach-ixp4xx
WAN driver code = drivers/net/wan
Eth code = drivers/net/arm
Why would you want such placement?
Potential
[Added Lennert Buytenhek to CC list]
Hey again,
Code placement:
Queue Manager NPE code = arch/arm/mach-ixp4xx
WAN driver code = drivers/net/wan
Eth code = drivers/net/arm
Why would you want such placement?
Potential problems: header files would have to be moved to
include/asm-arm = headers
Having thought about it a bit more, a layout similar to the one
proposed by you may make sense.
Michael-Luke Jones [EMAIL PROTECTED] writes:
Despite their name, Network Processing Engines are independent
coprocessors which are only coincidentally attached to MACs for
ethernet / WAN purposes.
Christian Hohnstaedt [EMAIL PROTECTED] writes:
- the NPE can also be used as DMA engine and for crypto operations.
Both are not network related.
Additionally, the NPE is not only ixp4xx related, but is
also used in IXP23xx CPUs, so it could be placed in
arch/arm/common or
On 7 May 2007, at 01:07, Krzysztof Halasa wrote:
Adds IXP4xx drivers for built-in CPU components:
- hardware queue manager
- NPE (network coprocessors),
- Ethernet ports,
- HSS (sync serial) ports (currently only non-channelized HDLC).
Both Ethernet and HSS drivers use queue manager and NPE
20 matches
Mail list logo
