From: Gilad Rom <gilad@romat.com>
To: Zoran Stojsavljevic <zoransto@dkts.co.yu>
Cc: Alex Zeffertt <ajz@cambridgebroadband.com>,
linux-atm-general@lists.sourceforge.net,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: [Linux-ATM-General] Fw: MPHY supported in mpc8260sar
Date: Wed, 18 Aug 2004 10:45:25 +0300 [thread overview]
Message-ID: <1092815125.28273.24.camel@gilad.lan> (raw)
In-Reply-To: <000f01c484f5$6c7298c0$30c8a8c0@zorans>
And exactly how many PHY's is that?
Gilad.
On Wed, 2004-08-18 at 10:31, Zoran Stojsavljevic wrote:
> I enhanced 8260 ATM driver... now I am able to support maximum number
> of PHYs by mpc8260. With up to eight priorities per each PHY.
>
> Just an additional info... :)
>
> ----- Original Message -----
> From: "Zoran Stojsavljevic" <zoransto@dkts.co.yu>
> Sent: Thursday, August 05, 2004 11:09 AM
> Subject: MPHY supported in mpc8260sar
>
> > I finally achieved multiphy mpc8260sar (with some limitations). The
> > driver is able to support 8 PHYs (one PHY per unique priority). The
> > driver is developed out of Peter's McCormick single PHY version.
> >
> > For some unknow reason I could NOT achieve MPHY support with only
> > one priority (for example highest PRIority 0). In order to make MPHY
> > to work correctly I assigned a unique priority per PHY. With 8 PHYs
> > the mapping looks like: PHY0/PRIO0, PHY1/PRIO1... PHY7/PRIO7, eg.
> > PHYx/PRIOx, where x is in range [0..7]!
> >
> > The another limitation is that I did NOT fix the VP range, eg. I am
> > using only VP0 (one VP) with different VCs, where least three (3)
> > significant bits of each VC assume the selected PHY. In other words,
> > I am using 8 nas interfaces, and VCs (decimal radix) from 40 (0x28)
> > to 47 (0x2F), where VC 40 is attached to PHY0, VC 41 to PHY1... VC47
> > to PHY7. While issuing ATM xmit command I am deriving least three
> > significant bits of currently processed VC and I'm putting them to
> > the COMM_INFO words (offset 0x86, field PHY#), described in section
> > 30.14 of MPC8260 PowerQUICC II Family Reference Manual (Revision 1,
> > date 05/2003).
> >
> > If you all find this info of (some) interest, I can do the patch
> > (against latest version in CVS) so we can store this limited edition
> > of the MPHY version under the mpc8260sar driver project.
> >
> > ----- Original Message -----
> > From: "Alex Zeffertt" <ajz@cambridgebroadband.com>
> > Sent: Monday, January 26, 2004 1:41 PM
> > Subject: Announcement: MPHY now supported in mpc860sar
> >
> > > Just a quick note to say that multi-phy is now supported by the
> > > mpc860sar ATM driver, thanks to a patch by Rodolfo Giometti.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-18 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 7:31 Fw: MPHY supported in mpc8260sar Zoran Stojsavljevic
2004-08-18 7:45 ` Gilad Rom [this message]
2004-08-18 8:36 ` [Linux-ATM-General] " Zoran Stojsavljevic
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=1092815125.28273.24.camel@gilad.lan \
--to=gilad@romat.com \
--cc=ajz@cambridgebroadband.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=zoransto@dkts.co.yu \
/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).