From: Kim Phillips <kim.phillips@freescale.com>
To: Steven Hein <ssh@sgi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 8360 custom board, ucc_geth TX errors on longer(?) packets
Date: Fri, 1 Feb 2008 13:53:24 -0600 [thread overview]
Message-ID: <20080201135324.8372268e.kim.phillips@freescale.com> (raw)
In-Reply-To: <47A36A69.1010809@sgi.com>
On Fri, 01 Feb 2008 12:52:25 -0600
Steven Hein <ssh@sgi.com> wrote:
> The one main difference in this board is how eth0 is wired.
> We have a Broadcom GbE switch part, and UCC1 eth is wired
> directly to that switch (no PHY). (This where I needed to
sounds like you ran into some h/w errata. if on rgmii, you might
want to find a way to program the switch for rgmii with internal delay
(8360 rev.2 rgmii-id rx & tx; 8360rev2.1 rgmii-rxid (i.e. for rx
only)). If not, I'd contact fsl tech support directly.
Kim
next prev parent reply other threads:[~2008-02-01 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 18:52 8360 custom board, ucc_geth TX errors on longer(?) packets Steven Hein
2008-02-01 19:53 ` Kim Phillips [this message]
2008-02-01 20:05 ` Steven Hein
2008-02-01 22:06 ` Steven Hein
2008-02-01 23:18 ` Kim Phillips
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=20080201135324.8372268e.kim.phillips@freescale.com \
--to=kim.phillips@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ssh@sgi.com \
/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).