From: Dan Malek <dan@embeddededge.com>
To: Rudolf Ladyzhenskii <rudolf.ladyzhenskii@act-aus.net>
Cc: "Linuxppc-Embedded (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ATM switching in MPC8260
Date: Wed, 05 Dec 2001 12:35:03 -0500 [thread overview]
Message-ID: <3C0E5AC7.4090203@embeddededge.com> (raw)
In-Reply-To: B164B53F5BD6D511888D009027732E1A0249AA@ntserver.act.domain
Rudolf Ladyzhenskii wrote:
> Hi, all
>
> I have to do some ATM traffic switching
I'm not sure what you mean by "traffic switching." The 603 core
needs to be involved for some management of the connections. I've
done custom Ethernet bridging applications over ATM using the AAL5
and it has worked well.
> MPC8260 manual says that it is possible to do it on AAL0
The AAL0 is just a "raw" ATM cell connection. Anything over this interface
requires 603 core interaction. It's purpose is to provide a conduit for
ATM cells that aren't configured for processing by CPM. Any VCI/VPI the
CPM receives that it doesn't understand is routed here.
> Does anyone know if this is possible for AAL5?
With AAL5 you just hand the CPM a PDU for transmit, and the receiver
returns the PDU in the receive buffer. The CPM does all of the cell
fragmentation, CRC and length checks, and header processing.
There are many nice features of this ATM controller, including things
like bit rate and cell scheduling. I suspect the whole of the Linux ATM
software can be done by the CPM (and then some), all we need is a data
path and control interface.
Have fun!
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-05 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 4:30 ATM switching in MPC8260 Rudolf Ladyzhenskii
2001-12-05 16:18 ` James Campbell
2001-12-05 17:35 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 22:18 Rudolf Ladyzhenskii
2001-12-06 0:41 ` Dan Malek
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=3C0E5AC7.4090203@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rudolf.ladyzhenskii@act-aus.net \
/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).