linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Kestener <pierre.kestener@cea.fr>
To: linuxppc-embedded@ozlabs.org, Pierre Kestener <pierre.kestener@cea.fr>
Subject: Virtex2pro OPB frequency 10/100Mbs ethernet link related problem
Date: Wed, 20 Apr 2005 11:46:42 +0200	[thread overview]
Message-ID: <42662502.5060108@cea.fr> (raw)

Hello,

I have noticed a strange behavior regarding NFS on my target (Virtex2pro 
ff1152 from Memec) when increasing OPB/PLB bus frequency from 50 MHz to 
66.666667MHz to be able to use a 100 Mbs ethernet link (it is mentionned 
in the OPB/EMAC IP doc
that Bus clock should be more than 65 MHz to have 100Mbs).

I use U-boot (ML300 port with small modifications) for the bootloader 
step (download linux kernel via tftp) and kernel 2.4.20. The root 
filesytem is mounted via NFS.

At 50MHz, everything works fine. Ethernet link speed is 10 Mbs. I can 
check that on my Ethernet switch.

When using 66.666667MHz OPB frequency, ethernet Link speed is indeed 
100Mbs. U-boot works perfectly but linux boot fails trying to get nfs 
server port !!!

Using "tcpdump" on my linux host, i can see that target sends ARP 
packets and the server replies but nothing happends...
 
    09:04:28.848228 arp who-has myHost.extra.cea.fr tell 132.166.xxx.yyy
    09:04:28.848265 arp reply myHost.extra.cea.fr is-at 00:06:5b:xx:yy:zz

Has anyone seen such a behavior, using a 100Mbs ethernet link with a 
Virtex2pro target ?
Any idea regarding this problem (hardware or software) ?

Thanks a lost.
Best Regards.

Pierre Kestener.

             reply	other threads:[~2005-04-20 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20  9:46 Pierre Kestener [this message]
2005-04-21 15:17 ` Virtex2pro OPB frequency 10/100Mbs ethernet link related problem Pierre Kestener

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=42662502.5060108@cea.fr \
    --to=pierre.kestener@cea.fr \
    --cc=linuxppc-embedded@ozlabs.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).