Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Peter 'p2' De Schrijver <p2@debian.org>
To: Jan Rovins <janr@adax.com>
Cc: David Daney <ddaney@caviumnetworks.com>, linux-mips@linux-mips.org
Subject: Re: linux 2.6.33 on movidis x16
Date: Fri, 19 Mar 2010 19:52:45 +0200	[thread overview]
Message-ID: <20100319175244.GH2437@apfelkorn> (raw)
In-Reply-To: <4BA277FB.6080808@adax.com>

Hi,

> You are right, it is called an x16.  My memory is failing me, I should  
> have looked at the machine first.
>

Ok :)

> from dmesg:
>
> cavium-ethernet: Cavium Networks Octeon SDK version 1.8.1, build 294
> Interface 0 has 4 ports (RGMII)
> Interface 1 has 4 ports (RGMII)
> Interface 2 has 4 ports (NPI)
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>
>
> looks like the PHYAD field has what you are loohing for,
> ethtool output: ---------------------------
>
> for i in 0 1 2 3 4 5 6 7; do ethtool eth$i; done
> Settings for eth0:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 10Mb/s
>        Duplex: Half
>        Port: MII
>        PHYAD: 1
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: no
> Settings for eth1:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 10Mb/s
>        Duplex: Half
>        Port: MII
>        PHYAD: 2
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: no
> Settings for eth2:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 10Mb/s
>        Duplex: Half
>        Port: MII
>        PHYAD: 3
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: no
> Settings for eth3:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Half 1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 10Mb/s
>        Duplex: Half
>        Port: MII
>        PHYAD: 4
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: no
> Settings for eth4:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 100Mb/s
>        Duplex: Full
>        Port: MII
>        PHYAD: 0
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: yes
> Settings for eth5:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 100Mb/s
>        Duplex: Full
>        Port: MII
>        PHYAD: 0
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: yes
> Settings for eth6:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 100Mb/s
>        Duplex: Full
>        Port: MII
>        PHYAD: 0
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: yes
> Settings for eth7:
>        Supported ports: [ TP MII ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 100Mb/s
>        Duplex: Full
>        Port: MII
>        PHYAD: 0
>        Transceiver: internal
>        Auto-negotiation: on
>        Link detected: yes
>

PHYAD 0 for ports 4 - 7 seems a bit strange to me. Do you have the sources of the
kernel you're running on those machines ? If so, could you look at 
int cvmx_helper_board_get_mii_address(int ipd_port) in cvmx-helper-board.c ?
It contains a large switch statement. case CVMX_BOARD_TYPE_CUST_WSX16: is what I'm
interested in.


> ----------------------------------------------------------
> You may want to re-map the interfaces so that they show up in a sane  
> order, there is a cluster of 8 ethernet ports, 4 per row.  Right now on  
> our boxes , eth0 shows up on the bottom row, second  from the right.

Thanks,

Peter.

  reply	other threads:[~2010-03-19 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-05 14:11 linux 2.6.33 on movidis x16 Peter 'p2' De Schrijver
2010-03-15 22:27 ` Jan Rovins
2010-03-18 18:17   ` Peter 'p2' De Schrijver
2010-03-18 18:26     ` David Daney
2010-03-18 18:59       ` Jan Rovins
2010-03-19 17:52         ` Peter 'p2' De Schrijver [this message]
2010-03-19 20:27           ` Jan Rovins
2010-03-19 22:03             ` David Daney
2010-03-19 22:38               ` Jan Rovins
2010-03-19 23:00       ` David Daney
2010-03-21 16:00         ` Peter 'p2' De Schrijver

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=20100319175244.GH2437@apfelkorn \
    --to=p2@debian.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=janr@adax.com \
    --cc=linux-mips@linux-mips.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