linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Zoran Stojsavljevic" <zoransto@dkts.co.yu>
To: "Alex Zeffertt" <ajz@cambridgebroadband.com>,
	<linux-atm-general@lists.sourceforge.net>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: MPHY supported in mpc8260sar
Date: Thu, 5 Aug 2004 11:09:24 +0200	[thread overview]
Message-ID: <036601c47acb$e9e0cc70$30c8a8c0@zorans> (raw)
In-Reply-To: 1075117282.1504.17.camel@zambia.cambridgebroadband.com


Hello to all,

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.

Best Regards,
Zoran Stojsavljevic
DKTS Pupin Telecom
zoransto@dkts.co.yu

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

      parent reply	other threads:[~2004-08-05  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 11:41 Announcement: MPHY now supported in mpc860sar Alex Zeffertt
2004-01-26 13:51 ` [Linux-ATM-General] " Gilad Rom
2004-01-26 13:59   ` Alex Zeffertt
2004-01-26 14:03     ` [Linux-ATM-General] Announcement: MPHY now supported inmpc860sar Gilad Rom
2004-01-26 14:17       ` Alex Zeffertt
2004-02-05 12:54       ` Zoran Stojsavljevic
2004-02-05 13:43         ` Alex Zeffertt
     [not found]         ` <007101c3ec8c$3ea8eae0$80227c92@intranet.gr>
2004-02-10  7:32           ` Zoran Stojsavljevic
2004-01-27  7:41 ` Quick ad-hoc question? Zoran Stojsavljevic
2004-08-05  9:09 ` Zoran Stojsavljevic [this message]

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='036601c47acb$e9e0cc70$30c8a8c0@zorans' \
    --to=zoransto@dkts.co.yu \
    --cc=ajz@cambridgebroadband.com \
    --cc=linux-atm-general@lists.sourceforge.net \
    --cc=linuxppc-embedded@lists.linuxppc.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).