From: Steven Hein <ssh@sgi.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 8360 custom board, ucc_geth TX errors on longer(?) packets
Date: Fri, 01 Feb 2008 16:06:15 -0600 [thread overview]
Message-ID: <47A397D7.30809@sgi.com> (raw)
In-Reply-To: <47A37B8E.5000500@sgi.com>
Steven Hein wrote:
> Kim Phillips wrote:
>> 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
>>
>
> I would suspect HW.....but this WORKS with the 2.6.16 kernel
> I was using! That's why I suspect that I still don't have
> something configured right in my device tree, or something
> else I missed in the new kernel. But I can't
> figure out what it is.... :-( I've poured over the code in
> the old versus new (both the ucc_geth driver and the platform
> initialization in the old, and the device tree in the new)
> and can't figure out what I missed! And like I said, a
> kernel with the same config (other than changing the platform)
> works on my MPC8360E-MDS board. Granted, that doesn't have
> this direct switch connection......
>
> I did look at the code related to the HW errata (QE_ENET18).
> But we're using GMII to the switch....and that workaround
> code wasn't in active in my old kernel (it was there, but
> commented out).
>
> Any other thoughts? Has anyone seen this symptom before?
>
> Steve
>
Okay....I found it! Started poking at the UCCE registers
and found that the FIFO sizes weren't right. This led me
to find a bug in my ucc_geth interface to the fixed-link
PHY driver: the code to reconfigure the MURAM FIFO's for
Gigabit operation wasn't being executed for no-phy configs!
All is well once I changed this.
Sorry for the noise..... (glad I found this before
submitting my patch! ;-)
Steve
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Steve Hein (ssh@sgi.com) Engineering Diagnostics/Software
Silicon Graphics, Inc.
1168 Industrial Blvd. Phone: (715) 726-8410
Chippewa Falls, WI 54729 Fax: (715) 726-6715
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2008-02-01 22:06 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
2008-02-01 20:05 ` Steven Hein
2008-02-01 22:06 ` Steven Hein [this message]
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=47A397D7.30809@sgi.com \
--to=ssh@sgi.com \
--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).