From: "André Schwarz" <andre.schwarz@matrix-vision.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Link problem with eTSEC2 on P2020RDB
Date: Wed, 23 Jun 2010 08:14:02 +0200 [thread overview]
Message-ID: <1277273642.2010.2.camel@swa-m460> (raw)
In-Reply-To: <4C211735.7080309@embedded-sol.com>
Felix,
nice to hear that your problem is fixed.
Since I'm using VSC8601 PHY with RGMII interface this looks like a
different issue.
Cheers,
Andr?
On Tue, 2010-06-22 at 23:04 +0300, Felix Radensky wrote:
> Hi,
>
> eTSEC2 is unusable with TOT master on P2020RDB RevC. The following
> example demonstrates the problem:
>
> => setenv ethact eTSEC2
> => ping 10.0.0.10
> Waiting for PHY auto negotiation to complete...... TIMEOUT !
> eTSEC2: No link.
>
> eTSEC2 on P2020RDB is connected to Vitesse SGMII PHY VSC8221.
>
> Git bisect shows that the problem was introduced by the following commit:
>
> 46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4 is first bad commit
> commit 46e91674fb4b6d06c6a4984c0b5ac7d9a16923f4
> Author: Peter Tyser <ptyser@xes-inc.com>
> Date: Tue Nov 3 17:52:07 2009 -0600
>
> tsec: Force TBI PHY to 1000Mbps full duplex in SGMII mode
>
> Reverting this commit makes the problem go away.
>
> Felix.
>
>
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Hans-Joachim Reich
next prev parent reply other threads:[~2010-06-23 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 20:04 [U-Boot] Link problem with eTSEC2 on P2020RDB Felix Radensky
2010-06-23 6:14 ` André Schwarz [this message]
2010-06-23 10:41 ` Aggrwal Poonam-B10812
2010-06-25 11:33 ` Felix Radensky
2010-06-26 5:22 ` Ben Warren
2010-06-26 10:09 ` Felix Radensky
2010-06-26 13:19 ` Peter Tyser
2010-06-29 7:58 ` Felix Radensky
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=1277273642.2010.2.camel@swa-m460 \
--to=andre.schwarz@matrix-vision.de \
--cc=u-boot@lists.denx.de \
/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