From: Jan Rovins <janr@adax.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Peter 'p2' De Schrijver <p2@debian.org>, linux-mips@linux-mips.org
Subject: Re: linux 2.6.33 on movidis x16
Date: Fri, 19 Mar 2010 18:38:17 -0400 [thread overview]
Message-ID: <4BA3FCD9.2020205@adax.com> (raw)
In-Reply-To: <4BA3F4AC.5000307@caviumnetworks.com>
David Daney wrote:
> On 03/19/2010 01:27 PM, Jan Rovins wrote:
>
>
>> case CVMX_BOARD_TYPE_KBP: /* JLR first Movidis X16 */
>> case CVMX_BOARD_TYPE_CUST_WSX16: /* JLR second Movidis X16 */
>> /* Board has 8 SGMII ports. 4 connect out, two connect to
>> a switch,
>> and 2 loop to each other */
>> if ((ipd_port >= 0) && (ipd_port < 4))
>> return ipd_port+1;
>> else
>> return -1;
>
> I don't think that is correct. I just verified that that PHYs are on
> addresses 0-7. That code makes them start at 1.
>
> The Octeon mdio bus driver also needs a small change.
>
> I am working on a patch.
You are most likely right.
using ipd_port+1 is probably what made my eth0 show up on the 2nd RJ45
port.
We were just using those boxes for early development, to verify basic
Octeon functionality of some of our hardware drivers, so once an
Ethernet port started working, I did not look into it any further, since
it was a temporary setup just to get things going.
I looked for the original source from Movidis, and all I found in their
kernel source were broken symlinks to a tool chain they that they did
not give me :-(
Jan
>
> David Daney
>
next prev parent reply other threads:[~2010-03-19 22:38 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
2010-03-19 20:27 ` Jan Rovins
2010-03-19 22:03 ` David Daney
2010-03-19 22:38 ` Jan Rovins [this message]
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=4BA3FCD9.2020205@adax.com \
--to=janr@adax.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=p2@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.